PopMenu DLL Documentation (3K)
VB5 PopupMenu DLL Binary (51K)
VB5 PopupMenu DLL Demonstration (78K)
VB5 PopupMenu DLL Full Source (184K)
VB6 PopupMenu DLL Binary (52K)
VB6 PopupMenu DLL Demonstration (76K)
VB6 PopupMenu DLL Full Source (185K)
Bugs: 12 / 13
Issues: 0 / 0
Questions: 0 / 0
23 Apr 2003
If an menu was used as a drop-down from a vbAccelerator Toolbar control, and it contained infrequently used items which were hidden, once the items were exposed they did not respond when clicked. Now all items click correctly.
When showing as a chevron in a menu, if you customised which buttons were visible they could incorrectly appear in the chevron menu.
Disabled items now draw in the correct colour when XP style is in effect.
Subclassing Without The Crashes
Child menus of disabled parents still fire click events in response to mnemonics
Summary
| Id: | 7.13 |
| Type: | Bug |
| Current Status: | Open |
Detail
| 19 Nov 2003 | Open | Steve McMahon |
The control was originally written to behave like the Office ones, and you’ll notice that the Office applications disable the submenu items rather than the parent (in general this it is better UI practice to do this). However, this should be fixed. A workaround is to check whether the item is Enabled when the click event fires. | ||
| 19 Nov 2003 | Open | Juan Marugán |
If you mark as disabled an option of a menu that has submenus, the submenus still work with the associated hotkeys. This happens at least when you have a main menu in an application built with the menu tool of VB and disabled one of these main menu options (File, Edit, View, etc). The rest of options hanging from the disabled one are not accessible with the mouse, but still working with the associated hotkey (Fx, Ctrl-Fx, etc). | ||
