Re: hilite 'sticking' in certain option menus and fields
I reported Bug 7982 on this, listed as minor. http://quality.runrev.com/qacenter/show_bug.cgi?id=7982 Also filed bug 7983 on strange menu behaviour, this ones a beauty, with a screenshot. http://quality.runrev.com/qacenter/show_bug.cgi?id=7983 2009/4/20 Martin Blackman martinblack...@gmail.com: Thanks Francis, setting the 'focusable' property ie traversalon to true makes the button retain its hilite after selecting which is probably expected behaviour. But it doesn't explain the first problem with the popup, I may bugzilla that. 2009/4/20 Francis Nugent Dixon effe...@wanadoo.fr: Hi from Paris, Martin, When you create your button by script, examine the Focus and the Show Focus options which may be selected. When you create a standard button with the IDE, these options are not selected, unless you create a Default button (hilited in blue). I haven't time to experiment, so this is a wild guess . -Francis The best things in life are Illegal, Immoral or Fattening . With one exception ... REVOLUTION ! ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
hilite 'sticking' in certain option menus and fields
Hi from Paris, Martin, When you create your button by script, examine the Focus and the Show Focus options which may be selected. When you create a standard button with the IDE, these options are not selected, unless you create a Default button (hilited in blue). I haven't time to experiment, so this is a wild guess . -Francis The best things in life are Illegal, Immoral or Fattening . With one exception ... REVOLUTION ! ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: hilite 'sticking' in certain option menus and fields
Thanks Francis, setting the 'focusable' property ie traversalon to true makes the button retain its hilite after selecting which is probably expected behaviour. But it doesn't explain the first problem with the popup, I may bugzilla that. 2009/4/20 Francis Nugent Dixon effe...@wanadoo.fr: Hi from Paris, Martin, When you create your button by script, examine the Focus and the Show Focus options which may be selected. When you create a standard button with the IDE, these options are not selected, unless you create a Default button (hilited in blue). I haven't time to experiment, so this is a wild guess . -Francis The best things in life are Illegal, Immoral or Fattening . With one exception ... REVOLUTION ! ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
hilite 'sticking' in certain option menus and fields
Hi List, In my stack I have an option menu button, on which the user can right-click to popup a context menu. As of version 3 and 3.5 of Rev on XP, when the popup menu appears, the option menu gets hilited and remains so (ie the background goes dark blue). This doesnt happen in version 2.9. The hilite will only toggle back to off if I do another popup operation. Clicking somewhere to remove focus doesn't do the trick. I found that changing the 'HiliteFill' property of the option menu to false prevents this happening, OR waiting for the mouse button to be released before popping up the popup button also prevents it. But this doesn't happen with all option menu buttons. My option menu button is generated by script. If I create a button in the IDE by dragging from the tools pallet I don't get the same behaviour. As a related issue I am having problems with some other option menu buttons and fields created by script in a group . The fields get their text selected when I tab into them and the hilite remains when you click outside the group. I think this is caused by having the autotab of the fields set to true - but why should that cause the fields to hilite differently ? The menu buttons in the same group also remains hilited when I select a choice, which doesn't seem right. Does anyone have any thoughts on whether these behaviours are correct ? thanks Martin ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution