-
-
Notifications
You must be signed in to change notification settings - Fork 975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Excessive status bar height #1728
Comments
This is a reasonable compromise for platform independence too. On other OS or different OS font settings the gaps are smaller. The minimum height was chosen with a safety offset to avoid clipping as reported in #1010. Concerning the alignment between coordinates and mouse button hints, there is no relation between those widgets. There are always two lines in coordinates, but there can be 1-3 lines in mouse button hints. |
That's a pity we can't have more subtle status bar. However we can easily Disable/Enable the Status Bar at any moment. |
I found the mouse widget is spanning the whole status bar height. |
I think that slightly reducing the mouse icon would be the simplest and the most effective way. |
need to test the impact on high dpi monitors |
The status bar height looks somewhat excessive, taking up quite a lot of space on the laptop screen.
I remember this is a long-standing feature of LibreCAD UI rather than a bug. However, is it possible to make the status bar less beefy?
For instance, here I highlighted the vertical gaps that could have been diminished.
Also, it looks to me that mouse button action hints appear too high, above the upper string of the status bar.
It is expected to see it in one level with the line of Cartesian coordinates.
It seems that issue was partially addressed in #1410
LibreCAD version info
Version: 2.2.0.2
Compiler: Clang 13.0.0
Compiled on: Jul 29 2023
Qt Version: 5.15.10
Boost Version: 1.82.0
System: macOS 12.7
Operating System info
System Version: macOS "Monterey" 12.7.2 (21G1974)
Kernel Version: Darwin 21.6.0
MacBook Pro (14-inch, 2021)
The text was updated successfully, but these errors were encountered: