strange option menu behavior

Jan Schenkel janschenkel at yahoo.com
Fri Feb 12 17:35:09 CST 2010


That sounds like the standard behavior of option menus on Windows - there's no way to disable any of the menu items (nor to insert separator lines, for that matter). The same goes for combo-boxes, by the way.
The only solution I've been able to cook up, is to use a popup menu - use the 'at' parameter of the 'popup' command to make the menu appear in a fixed spot rather than under the mouse.

HTH,

Jan Schenkel
=====
Quartam Reports & PDF Library for Revolution
<http://www.quartam.com>

=====
"As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)


--- On Fri, 2/12/10, Chris Sheffield <cmsheffield at gmail.com> wrote:
> I may be doing something that option
> menus were not intended for, so I want to check if others
> are seeing the same behavior.
> 
> Using Rev 4.0, I'm creating an option menu in a stack with
> all the possible menu items I need in it. However, some of
> these menu items need to be disabled at different points. So
> I'm simply running a "disable menuitem 2" command, and that
> works great on the Mac side. But when I do this on the
> Windows side, the menu items do not appear disabled, and
> they're displaying the "(" before the "disabled" items.
> What's strange, though, is when I select one of these items,
> my menuPick handler does not fire, but the menuHistory of
> the button changes to the item I selected. So there's kind
> of some weird mixed behavior going on.
> 
> Anyone else seeing this? Is it normal? Is there a
> workaround? Should I not be using an option menu this way?
> 
> Thanks for any suggestions.
> 
> Chris
> 
> 
> --
> Chris Sheffield
> 


      




More information about the use-livecode mailing list