-
Bug
-
Resolution: Fixed
-
P4
-
None
Many of the controls and containers have the height properties listed above their width properties. This is bad practice. Width before height please. This includes Max Width, Min Width, Pref Width - they should all be listed above their height counterpart. Also, we should not separate properties that are paired and try to group similar properties together.
Lets use AnchorPane as an example. The Layout Tab > Region Section currently has this property order:
Height
Max Height
Max Width
Min Height
Min Width
Padding
Pref Height
Pref Width
Snap to Pixel
Width
A more user friendly property order would be:
Width
Height
Max Width
Max Height
Min Width
Min Height
Pref Width
Pref Height
Padding
Snap to pixel
Notice all the properties to do with width and height are grouped ( Padding and Snap to pixel are not connected to width and height and are therefore added afterwards). Also, Width and Height follow one another which is to be expected. In the current implementation (which uses a simplistic alphabetical approach) Width and Height are at opposing ends of the list!
Lets use AnchorPane as an example. The Layout Tab > Region Section currently has this property order:
Height
Max Height
Max Width
Min Height
Min Width
Padding
Pref Height
Pref Width
Snap to Pixel
Width
A more user friendly property order would be:
Width
Height
Max Width
Max Height
Min Width
Min Height
Pref Width
Pref Height
Padding
Snap to pixel
Notice all the properties to do with width and height are grouped ( Padding and Snap to pixel are not connected to width and height and are therefore added afterwards). Also, Width and Height follow one another which is to be expected. In the current implementation (which uses a simplistic alphabetical approach) Width and Height are at opposing ends of the list!