Window Framework v1.2.4
Window Framework for Unity UI Toolkit
Loading...
Searching...
No Matches
Changelog

Official Website:

Unity Asset Store:

YouTube Tutorials and Videos:

Changelog:

1.2.4 Doxygen Integration and expanded documentation

  • We are now using Doxygen for all of our software, this means that comment blocks will be expanded and will serve as the generation code for the online documentation.
  • Documentation is getting a new home on our site: https://docs.garage-ware.com

1.2.3 Unity 6.3 updates Verified compatability with all patched Unity versions and 6.3 beta

  • Changed icons to use SVG images, no changes are needed for existing projects. Old icons remain for now but will eventually be removed.
  • Cleanup of the theme manager window layout, themes should now be easier to read in both light and dark editor mode
  • Cleanup of the debugger window layout, themes should now be easier to read in both light and dark editor mode

1.2.2 Minor Update

  • Changed main window content from a ScrollView to a visual element. if a scroll view is needed then you will need to create on in your content element. This will fix the double horizontal scroll bar issue happening on some popular control elements.

1.2.1 Minor Updates

  • Fixed WindowFrame requirement for a context menu. Adding a context menu to a non-window frame should now work properly
  • Added more documentation
  • fixed bug where windows with proper window id and parent id forget their location on reopening.

Changelog: 1.2.0 Changes to the Theme System / Framework Upgrades and bug fixes

  • Added Global Stylesheets list for items that are used in all of your themes, such as the SlideToggle example object, since this item will always have the same stylesheet no matter what theme selected is. This keeps you from having to add the same stylesheet to every theme.
  • Global Stylesheets allow both StyleSheet (USS) asset or a Unity Theme asset (TSS) to be assigned. TSS is the recommended approach, but it is not required. This 'global' stylesheet is where you can store style that apply to all themes. Things like specific form elements or layout sizing can be done here.
  • Added an option to the Window Frame Controller that lets you choose to load the Global Stylesheets first or last.
  • The theme stylesheet is now restricted to a Unity Theme (TSS) or Runtime Theme assets, previously you could use either but based on feedback it was confusing. This change allows for better integration into the Unity Theme system and reinforces a modular approach to resource creation.
  • Properly created themes are now displayed in the Theme selector at the top of UI Builder so you can quickly switch scenes on the StylingScratchPaper.uxml document. (To refresh, the StylingScratchPaper.uxml file is a UXML document with a single WindowFrame custom control placed so you can experiment with your stylesheets)
  • Update the theme list with a new cleaner look
  • Created several themes (Light, Dark, Pastel, Halloween, Thanksgiving, Christmas) to better demonstrate the intended theme setup
  • Added the ability to apply theme stylesheets to the Window Frameworks parent panel. When enabled the system will apply the stylesheets to the panel that the WindowFramework is using, making the styling available to all Visual Elements in the panel, not just the Window Frames.
  • Added the ability to apply theme stylesheets to all panels. when selected, the system will attempt to find all active panels and apply the theme stylesheets to them.
  • Moved all editor-based files to the dedicated Editor folder; this includes all assets that are used in the editor only (scripts, resources, etc)
  • Stylesheets folder is now Themes. The Themes folder contains a sub-folder for each theme with all stylesheet (USS and TSS) files included.
  • Seperated all stylesheets into individual items in each theme folder.
  • Phased out all UGUI editor displays, all editor screens now use UIToolkit based forms.
  • Added the SlideToggle custom control, based on the sample from Unity Docs, it has been cleaned up and documented.
  • Added additional error checking of values during reload of save data.
  • Cleaned up documentation and added more inline comments to work better with Intellisense enabled editors
  • Added Fullscreen toggle from window options menu, uses new flags AllowFullscreen and LockFullscreen
  • Added Flag AllowFullscreen which allows toggle of window to full screen mode
  • Added Flag LockFullScreen which when set to true will force the window to be and stay full screen
  • Added Flag AllowMultipleInstances to windowframes (default = true) when set to false, the system will find and bring to front the existing window instead of creating a new one
  • Added New WindowFrame Controller Debug Window (editor based), access at Tools/Garage-Ware Games/Window Framework/Controller Debug Window
  • Improved timing and fades for tooltips and context menus
  • Added show delay to tooltips, tooltips now have a fadedelay and a showdelay as seperate values.
  • Tooltips now have a selector for fade type; Fade Out, Fade in, Fade In and Out, None
  • Created form element custom controls for settings sections that you can add into UI Builder UXML documents; Tooltip Settings, Context Menu Settings, Theme Settings
  • Defined USS variables for styling options
  • Added some additional icons and cursors:
  • https://www.flaticon.com/free-icons/ icons created by Pixel perfect - Flaticon
  • https://www.flaticon.com/free-icons/grab Grab icons created by berkahicon - Flaticon
  • Info icons created by Freepik - Flaticon

1.1.1 Fixed InputActions error when launching the demo scene in Unity 6.1

1.1.0 1.0.4: Added Context menu activator manipulator for right-click context menus on Visual Elements.

  • Fixed the missing 'Generate Demo Window' button in the demo scene.
  • Context menus now respect screen boarders.
  • ContextMenus now always use the WindowFrameController timing values to ensure proper synchronization.
  • You can now add a ContextMenuActivator manipulator to any VisualElement and enable right-click context menus, You must create the config object in code and pass it in at creation of the manipulator. For example, if you have a VisualElement called myNewElement, you can add the manipulator like this:
    myNewElement.AddManipulator(new ContextMenuActivator(ContextMenuConfig));
    1.0.3: Fixed problem where UI document reference may be lost.
  • You can now optionally assign the UI document in the inspector of the WindowFrame Controller. 1.0.2: Cleanup of informational debug statements 1.0.1: Fixed error causing context timers not to update in realtime. 1.0.0: Initial release with basic window management features.