Issue 31212 — Tree widget: The Value Changed trigger is not fired under certain circumstances
Status: Solved in 10.2.01
Solution available in patch(es): X801 MG01
Summary: The doubleClick trigger of the tree activates a form. Double-click the same item twice. Double-click another item The <VALC> trigger of a Tree widget (List View) is now not fired Environment: * Uniface versions: 9.6.07 (i.e. 9.6 + service pack MX06) and later * Operating System: OS independent * Database: DBMS independent Symtoms: 1. The doubleClick trigger of the tree activates a form. 2. Double-click the same tree item twice. 3. Double-click a different tree item Actual: The <VALC> trigger of the Tree widget (List View) is not fired Expected: The <VALC> trigger of the Tree widget (List View) should fire An example: 1. A Tree widget uses Extended Trigger <doubleClick> trigger doubleClick params string control: in ; TREE | LIST | KEYBOARD string item: in endparams message/hint "[doubleClick] - [%%tree%%%] selected." putmess "[doubleClick] - [%%tree%%%] selected." activate "B31212FRMCHILD".xEdit(tree.dummy) end ; trigger doubleClick 2. The <VALC> trigger of the Tree widget has code: message/hint "[VALUE CHANGED] [%%tree%%%] selected." putmess "[VALUE CHANGED] [%%tree%%%] selected." 3. Double-click item A1 4. Close the form that has been activated 5. Double-click the same item A1 6. Close the form that has been activated 7. Double-click another item B1 Result is that the form displays the wrong value because previously <VALC> did not fire.
There is no workaround for this problem
This problem is solved. Please pay attention to the following: when you activate the other form in the doubleClick trigger, the triggers which come later are ignored, because the other form has focus. This means that the Detail trigger by double-clicking the different item, or Detail and Value Changed (VALC) trigger by double-clicking the already selected item are not fired anyway - even after the fix. This behavior is the same as before Uniface MX06 / 9.6.07.