| [ Return to Bugs & Features | SVN ⇄ GIT ]
STR #2314
Application: | FLTK Library |
Status: | 2 - Closed w/o Resolution |
Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
Scope: | 3 - Applies to all machines and operating systems |
Subsystem: | Core Library |
Summary: | Width option for the Fl_Menu_Item |
Version: | 1.4-feature |
Created By: | mr.muscolo |
Assigned To: | AlbrechtS |
Fix Version: | Will Not Fix |
Update Notification: | |
Trouble Report Files:
No files
Trouble Report Comments:
|
#1 | mr.muscolo 22:44 Feb 04, 2010 |
| It would be nice to be able to specify such an option as width for the menu items. This way it would be easier to make all the menus (not menu bar but drop down menu from it) of some standard width.
For example: struct Fl_Menu_Item { const char* text; // label() ulong shortcut_; Fl_Callback* callback_; void* user_data_; int flags; uchar labeltype_; uchar labelfont_; uchar labelsize_; uchar labelcolor_; uchar entrywidth_; !!!!!!!! }; | |
|
#2 | matt 05:50 Feb 26, 2010 |
| I am not too happy with this idea. There ma be issues with alignment and size calculation which could be nicer if we had a professional designer on-board, but a general menu width seems to disrupt the design.
Open for discussion ;-) | |
|
#3 | matt 13:34 Feb 26, 2010 |
| Upping to 1.4 for now | |
|
#4 | AlbrechtS 18:51 Jan 15, 2023 |
| The 'entrywidth_' as proposed would be per menu *item*. This wouldn't make sense since all menu items must be packed in a common menu window which must be of a certain width (determined by all menu items).
OTOH, a maximal *menu* width (stored somewhere in the menu widget) could be useful as a constraint to fit all menu items into. Menu items larger than this width would have to be truncated though, which would be a UI problem.
That said, this STR won't fix and I'll close it now, but ...
@mr.muscolo: if you are still interested in such a feature, please discuss this in fltk.coredev and explain what exactly your issues are and what problems you'd like to solve. Maybe there are other solutions.
https://groups.google.com/g/fltkcoredev | |
[ Return to Bugs & Features ]
|
| |