That works!Josef Templ wrote:fixed.
The tests had a dependency on the order of menus due to a subtle bug in hotkey handling.
Build http://blackboxframework.org/unstable/i ... a1.706.zip contains the fixes.
- Josef
-Doug
That works!Josef Templ wrote:fixed.
The tests had a dependency on the order of menus due to a subtle bug in hotkey handling.
Build http://blackboxframework.org/unstable/i ... a1.706.zip contains the fixes.
- Josef
I think that needs to be expanded and clarified with examples.A nested menu is defined very much like a top-level menu except that its name must start with the character "$". In order to reference such a menu in a menu item, use the name of the nested menu (including the leading "$") as the action string. Menus can be nested at arbitray depth and it is also possible to reference a menu multiply.
Sure, but before finalizing the docu we should agree on the final formatDGDanforth wrote: I think that needs to be expanded and clarified with examples.
-Doug
Code: Select all
INCLUDE "Dev"
INCLUDE "Text"
INCLUDE "Form"
INCLUDE "Sql"
INCLUDE "Obx"
INCLUDE "*"
Currently I would not change the menu structure at all. This would be outside of this issue.Ivan Denisov wrote:Josef, how do you suggest to optimize menus structure? Can you include your ideas in that demo?
That I like.Ivan Denisov wrote:If it is possible without big change in the code I would prefer
NESTED "$my nested menu"
..
END
END
Leave it as it is for version 1.7.x and left the introduction of a new keyword to version 1.8 Then you have the whole freedom to change your mind after working it out.Josef Templ wrote: Currently it is not possible to have a normal top-level menu that starts with the letter "$"
because $ is used as an indicator that a menu is a nested menu. I think this is not a big problem
but it needs to be agreed on because it is a hard-coded limitation of the possible menu names.
The alternative would be ...
Simply append it. That should be done for 1.7.x and all the other solutions left for 1.8Josef Templ wrote: The idea is to support something like "menu extensions", i.e. extending an existing menu with the same
name instead of creating a new one even if it has the same name.
For example "Help": An extension package should be able to add a menu item to the Help menu.
This could also be applied to SQL and COM, which have Help items in their menus.
Another extension package (Srcnav, for example) may want to add a menu item to the Info menu.
But detail problems will arise in particular the question where to insert an extension unless it is simply appended.
Besides technical problems and complications, this uses a sub-optimal wording.DGDanforth wrote:That I like.Ivan Denisov wrote:If it is possible without big change in the code I would prefer
NESTED "$my nested menu"
..
END
END