Difference between revisions of "UI Floaters"
Jump to navigation
Jump to search
Line 23: | Line 23: | ||
** Note: Use bottom *or* bottom_delta, never both. | ** Note: Use bottom *or* bottom_delta, never both. | ||
***Note: All floaters, panels and widgets appear to accept these, so I will simply refer to them as " | ***Note: All floaters, panels and widgets appear to accept these, so I will simply refer to them as "coordinates" rather than spell them out for each file. | ||
===Generic Floater XML Elements=== | ===Generic Floater XML Elements=== |
Revision as of 21:18, 9 September 2007
This is a first stab and documenting the current xml file format as used in the Second LIfe viewer. Its not meant to be pretty, just useful (I hope).
The only conventions I can find defined on the wiki are as follows:
Adjust the Size of Widgets and Interface Elements
You will see the following information in XML files as well. This is what it means:
Width and Height
- width="100" // sets the width of the widget to be 100 pixels
- Note: This is the entire width of the widget, not just the label.
- height="20" // sets the height of the widget to be 20 pixels
- Note: This is the entire width of the widget, not just the label.
Left
- left="10" // sets the horizontal position of the left edge of the widget to be 10 pixels from the left edge of the panel or floater
- left_delta="100" // sets the horizontal position of the left edge of the widget to be 100 pixels from the left edge of previously listed widget
- Note: Use left *or* left_delta, never both.
Bottom
- bottom="300" // sets the vertical position of the bottom edge of the widget to be 300 pixels from the bottom edge of the panel or floater
- bottom="-30" // sets the vertical position of the bottom edge of the widget to be 30 pixels from the top edge of the panel or floater
- bottom_delta="-30" // sets the vertical position of the bottom edge of widget to be 30 pixels from the bottom edge of previously listed widget
- Note: Use bottom *or* bottom_delta, never both.
- Note: All floaters, panels and widgets appear to accept these, so I will simply refer to them as "coordinates" rather than spell them out for each file.