| [ Return to Bugs & Features | SVN ⇄ GIT ]
STR #3461
Application: | FLTK Library |
Status: | 1 - Closed w/Resolution |
Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
Scope: | 3 - Applies to all machines and operating systems |
Subsystem: | Core Library |
Summary: | Follow up to: [RFE] STR #2927: Please make 'LEADING' constant in FL_Menu.cxx an alterable API method |
Version: | 1.4-feature |
Created By: | chris |
Assigned To: | matt |
Fix Version: | 1.4.0 |
Fix Commit: | f4620329f16ed92e938a42d6c5803ed5061f1b45 |
Update Notification: | |
Trouble Report Files:
Trouble Report Comments:
|
#1 | chris 01:27 Apr 01, 2018 |
| (STR 2927 is already closed, so filing a new one)
I was trying this new feature with the 'menubar' test program an notice that with higher values of menu_linespacing (say from about 20 on) it can be cleary seen, that the top and bottom menu entries are cut off early.
Attaching a patch that I somehow figured out.
I think one of the 'LEADING' instances was wrong always and should have been just '4'. The other change is the correction of the Y offset from where the menu item are drawn (I found this by trial and error, can't say if it is really 'correct'.
Related: I was wondering, if the menu_linespacing could not be a property of the menu too (like it is with scrollbar_width), so it can be changed individually for a single menu, not just globally. | |
|
#2 | matt 04:45 Jan 20, 2023 |
| Fixed in Git repository.
Thx! | |
[ Return to Bugs & Features ]
|
| |