FWD » Core Development » User Interface

Eugenie found this list of bugs (testing with branch 4335a) while running the radio-set testcases (in testcases/uast/):

1. Widget is not highlighted(color must be changed) on mouse hover in Windows8 theme(all tests)
2. The widget size(width and height) is calculated incorrectly when size is not explicitly specified(1-3 pixels difference)(All tests with implicit size. rs_test0*.p for example).
3. Tooltip behavior is different. Tooltip position changing in 4gl when moving from one button to another, like the tooltip owner is the button, not radio-set, the text is the same. In FWD the tooltip acts as belonging to the whole radio-set(rs_test5.p).
4. FORM statement does not enable radio-set which is initially disabled, screen value is different(rs_test7.p).
5. ENTRY event handling deviation(rs_test8.p).
6. MODIFIED handling is different, initial value is different for MODIFIED attribute(rs_test8.p, rs_test9.p).
7. In 4GL the accelerator key char is not underlined with & prefix, while in FWD it is underlined(test-radio-set-1.p).

Test uast/radio_set/rs_test7_1.p

This test:

message "Hit a key to start".
pause.

def var ch as char view-as radio-set radio-buttons "a", "1", "b", "2".
def var num as int init 2 view-as combo-box list-item-pairs "One", 1, "Two", 2, "Five", 3.
def var flag as char init "true" view-as selection-list list-item-pairs "Happy", "Pappy", "After a While", "Crocadile" size 25 by 5.
def var txt as char init "".

form ch num flag txt with frame f1 side-labels.

/* ? 1 ? */
message ch:screen-value num:screen-value flag:screen-value.

ch:radio-buttons = "c,3,d,4".
num:list-item-pairs = "One,1,Two,2,Three,3".
flag:list-item-pairs = "On,true,Off,false,Oui,yes,Non,no".

/* 3 ? ? */
message ch:screen-value num:screen-value flag:screen-value.

/* realize everything */
enable all with frame f1.

ch:radio-buttons = "e,5,f,6".
num:list-item-pairs = "OneOne,11,TwoTwo,22,ThreeThree,33".
flag:list-item-pairs = "Off,false,On,true,Non,no,Oui,yes".

/* 3 1 ? */
message ch:screen-value num:screen-value flag:screen-value.

Results in:

1 ? ?
3 ? ?
5 ? ?

? ? ?
3 ? ?
5 ? ?

Test uast/radio_set/rs_test8.p

This test:

message "Hit a key to start".
pause.

/** Define widgets **/
define variable Rs as character initial "One" 
    view-as radio-set radio-buttons "One", "1", "Two", "2" , "Three", "3".
/* define variable Stat as logical. */
define variable RsValue as character.

define button ExitButton label "Exit".

/* Define frames */
define frame f0
   Rs ExitButton
with side-labels size-chars 60 by 15 centered title "Modified attribute radio-set, test #8".

/* Trigger definitions */

on value-changed of Rs
   do:
      RsValue = Rs:screen-value.
      message "The value changed to: " RsValue.
   end.

on entry of Rs
   do:
      message "ENTRY event received, RADIO-SET:MODIFIED is: " Rs:modified.
   end.

message "RADIO-SET:MODIFIED is: " Rs:modified.

enable all with frame f0.

message "RADIO-SET:MODIFIED is: " Rs:modified.

wait-for choose of ExitButton.

Results in:

RADIO-SET:MODIFIED is: yes
ENTRY event received, RADIO-SET:MODIFIED is: yes

RADIO-SET:MODIFIED is: no
ENTRY event received, RADIO-SET:MODIFIED is: no

Results from #4557-3, #4557-4, and #4557-5 were found using 3821c_13187