Argh...
This code lies in the IDE -
This imples that when a "check-type" menu is selected by the user, that nothing actually happens to the menu item, and the developer has to do the work of "checking" or "unchecking" it.
Does this mean I have to break the functionality of my GTK menus and not have it check the item when the user checks it?
And there was me thinking this was how menus worked? ....
....The user checks the menu, the menu updates to show it's checked - and therefore when you ask it MenuChecked() it will know there and then if it is checked or not?
For GTK, I can replace the above code with :
which makes sense to me... ??
:-(
This code lies in the IDE -
Case MENUQUICKENABLED If quickenabled quickenabled=False UncheckMenu quickenable Else quickenabled=True CheckMenu quickenable EndIf
This imples that when a "check-type" menu is selected by the user, that nothing actually happens to the menu item, and the developer has to do the work of "checking" or "unchecking" it.
Does this mean I have to break the functionality of my GTK menus and not have it check the item when the user checks it?
And there was me thinking this was how menus worked? ....
....The user checks the menu, the menu updates to show it's checked - and therefore when you ask it MenuChecked() it will know there and then if it is checked or not?
For GTK, I can replace the above code with :
Case MENUQUICKENABLED quickenabled = MenuChecked(quickenable)
which makes sense to me... ??
:-(