LayoutEditor v1.0 RC1

Save/Load:
  absolute names (C:/LayoutEditor/Media/my.layout)
  relative names (../Media/my.layout)
  names from Ogre FileSystem (my.layout)
  save/load any *.layout file in Ogre FileSystem through drop list in save/load menu.

Controls:
  Keyboard:
    ESC                - exit or exit from test mode
    Ctrl + O, Ctrl + L - open file
    Ctrl + S           - save file
    Ctrl + Z           - undo
    Ctrl + Y           - redo
    Ctrl + T           - test layout
    Ctrl + R           - toggle relative coordinates for selected widget

    Keyboard arrows - move widget
    Shift           - omit grid when moving/resizing widget
    Delete          - delete selected widget and all child widgets
    Tab             - change selected sheet (for Tab widget only)

  Mouse:
    click on widget - select widget
	Ctrl + click    - select through (select several times for selecting parent widgeets)
    doubleclick on any widget in widget panel - create widget in center
    doubleclick on selected Tab - add Sheet

Hidden widgets can be selected only through combo with all widgets.
You can't move hidden widget.

Ignoreg properties:
"Message_Modal", "Window_AutoAlpha" and "Window_Snap" ingnored in edit mode (but this properties will be saved and will work fine in test mode and your application).

All possible values can be found in Media/LayoutEditor/widgets.xml
  For example if you want add you own skin in editor add your my_skin.skin file to Media/LayoutEditor/editor.xml
  and add <Property key="Skin" value="MySkin"/> to appropriate widget.

Items/Sheelt panel is used to add and edit List or ComboBox items or Tab sheets. Press enter to edit selected item.

UserData panel is used to add UserData to any widget. UserData is map of key value pairs. It used to store any needed info in widget.
Here is several examples:
  1. You can add some info data to all widgets and in runtime you'll get it by std::string info = widget->getUserData(key); and show popup with info about widget.
  2. You have 10 buttons and want to have one event handler for all. You can add in user data button number and read it in event handler to understand which button was pressed.
  3. UserData can be used for different localisations. You can write two pairs like (key="Caption_English" value="Start"), (key="Caption_Russian" value="Ñòàðò") and use them when you changing languages.