You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FlatLaf attempts to keep the height and width of the JComboBox/JSpinner controls in sync.
The Windows L&F in contrast doesn't do this. In our case, this is a problem since we offer to change the height of specific table rows (it's a tree table and each level can have different sizes, which helps making the table content easier to grasp).
Now there are certain cells where there's for example a datepicker consisting of a date and time component, meaning we have two of these combo-components in one cell. Since they are always keeping their right component parts width and height in sync, this ends up taking a lot of space, meaning the cell isn't usable.
Was this a concious decision or did it just happen to be like this? Personally I prefer the Windows way and would even default to do it that way. While it looks less slightly "clean", it's more useful.
If you need an example, I can do that too, but I hope I explained it good enough :D (Will do it tomorrow then, it's late)
The text was updated successfully, but these errors were encountered:
FlatLaf attempts to keep the height and width of the JComboBox/JSpinner controls in sync.
The Windows L&F in contrast doesn't do this. In our case, this is a problem since we offer to change the height of specific table rows (it's a tree table and each level can have different sizes, which helps making the table content easier to grasp).
Now there are certain cells where there's for example a datepicker consisting of a date and time component, meaning we have two of these combo-components in one cell. Since they are always keeping their right component parts width and height in sync, this ends up taking a lot of space, meaning the cell isn't usable.
Was this a concious decision or did it just happen to be like this? Personally I prefer the Windows way and would even default to do it that way. While it looks less slightly "clean", it's more useful.
If you need an example, I can do that too, but I hope I explained it good enough :D (Will do it tomorrow then, it's late)
The text was updated successfully, but these errors were encountered: