Opened 17 years ago
Closed 16 years ago
#27 closed defect (fixed)
Dropping a new font on menus doesn't work correctly
Reported by: | Gregg Young | Owned by: | Gregg Young |
---|---|---|---|
Priority: | trivial | Milestone: | Release_3.9 |
Component: | fm/2 base | Version: | 3.09 |
Keywords: | Cc: |
Description
When you drop a new font on the menu bar the font on the files and view menu don't change. The font changes on all the other menus and the "Files" and "View" on the bar change just not the menus.
Change History (5)
comment:1 Changed 17 years ago by
comment:2 Changed 17 years ago by
Owner: | Gregg Young deleted |
---|
comment:4 Changed 16 years ago by
Milestone: | → Release_3.9 |
---|---|
Owner: | set to Gregg Young |
Status: | new → assigned |
Version: | → 3.09 |
comment:5 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
This appears to be the result of the way the menus are built (see below). Since SetConditionalCascade? is used the menus don't really exits until opened so the fonts are dropped on nothing and the menu can't be dropped on while open. Perhaps making a single files menu and a view menu containing all the items for all frame windows and then use MM_REMOVEITEM to change on fly for each different frame window would work. MM_REMOVEITEM should be use instead of MM_DELETEITEM because item can be added back easily in the case of changing between the drives container focus and directory container focus. MM_DELETEITEM could be used for other windows.
Misc.c near 1567 HWND CheckMenu?(HWND * hwndMenu, USHORT id) {