2.0.0 WindowFramework 2.0
Added
- Tabbed windows and workspace layout
- Header-to-header tab docking, a themed sub-header tab bar, retained content/footer switching, and pointer tear-off into independent floating windows.
- Host-tab promotion and restoration of retained floating geometry when detaching tabs.
- Recorded tab membership and active-tab state for eligible identified application windows, with concrete reconstruction and controller/per-window memory participation.
- Snapping, docking and window behavior controls
- Magnetic alignment to screen edges and neighboring windows, with configurable distance and screen/window targets.
- Left/right pointer docking previews and tab docking into eligible occupied zones.
- DockTo/Undock APIs for left, right, top and bottom halves, maximized layouts, and retained floating geometry.
- WindowBehaviorSettingsFormElement and persisted snapping/docking preferences; refined double-click fullscreen and tear-off handling.
- Eight-directional resizing
- Four edge and four corner handles, directional resize deltas and cursor artwork, while retaining the bottom-right footer affordance.
- Resize interaction follows AllowResize, Locked, Fullscreen and resolved size constraints.
- Controller-owned modals and card queues
- ShowModal presentation for detached WindowFrames, one active dialog with queued requests, and linked-document interaction/focus ownership.
- CardElement header/footer and scrolling body within WindowModal queues, active-card focus, dismissal permissions and controlled closing transitions.
- Optional prompts and required-answer forms; application validation, cancellation, gameplay input and other UI documents remain application-owned.
- Editable-copy and issue dialogs use the existing modal system rather than a separate host.
- Player Themes
- Independent editable theme folders with theme.json, optional previews and supported raster images below the configured persistent-data root.
- Named-copy validation, unique player identities, staged output validation, cancellation before commit, and explicit refresh/selection.
- Export of supported prepared framework values, configured font identities and application-specific extensions; asynchronous rasterization of supported configured vectors.
- A 164-field portable framework catalog with typed ranges, contained image references, recoverable-value issue reports, unavailable entries and identity/default fallback.
- Existing Theme Settings actions for editable copies, folder access, refresh, selection and View Issues.
- Metadata-driven Developer Extensions
- Line-based WFWDevExt declarations for application-owned numeric, color and Texture2D image settings, with identities, defaults, labels/descriptions and explicit numeric constraints.
- Studio-generated fields, source-preserving writes, supported selector/property mapping and prepared namespace records for player overrides.
- The existing example.hotbar Demo connects its 18 declared settings to 44 prepared consumer rules in ToolbarWindowExample.
- Runtime binding reconciliation and cleanup; player values do not supply new selectors, classes, metadata bounds or executable code.
- Project-owned repository setup
- Guided creation from configured defaults, with theme data, controller prefab, blank root UXML and a new or shared PanelSettings asset.
- Ownership/reference validation, deliberate destinations and collection application-sheet configuration. Scene placement and Addressables assignment remain explicit workflows.
- Optional Visual Scripting integration — preview
- A package-detected assembly with 20 existing window, query, theme, tooltip/context-menu and event units.
- WindowScriptingBridge for configured GameObject-targeted Custom Events and public window/theme actions.
- The supplied seven-node sample is an unwired starter palette; graph wiring, targets and listening/application readiness are not automatic.
- Structured diagnostics and controller debugger
- WindowFrameTelemetry channel-based JSON diagnostics and controller/debugger controls for enabled telemetry.
- A tokenized debugger with throttled refresh, window search/filtering, state/capability cards, geometry details, Focus/Ping/Close and existing controller actions.
Changed
- Modern theme organization and stylesheet ownership
- Seven 2.0 looks: Default, Dark, Light, Pastel, Halloween, Thanksgiving and Christmas.
- Each stock modern theme has its own entry/settings/preview folder and owned Icons/Cursors; configured identities and existing asset GUIDs are retained where preserved by the folder workflow.
- Modern themes compose the configured native-control, framework-component and slide-toggle application roles, additional application rules, then selected theme settings.
- Semantic/component tokens coordinate window, tab, input, menu, modal, status, cursor and slide-toggle appearance. The retained primitive library is not a mandatory imported palette foundation.
- Legacy entries retain their separate rendering/upgrade workflow; no universal automatic custom-layout conversion or visual-parity guarantee is implied.
- Theme Studio and Theme Manager
- A split inspector/representative-preview workspace, Switch Theme drawer, metadata editing, format badges and separate EDITING/ACTIVE/DEFAULT roles.
- Project-wide repository browsing, selected-file badges, pinned ThemeData selection and shared application-sheet order editing with the essential roles kept first.
- Independent theme-folder duplication and separate legacy-to-2.0 output, with collision handling and unsupported appearance-dependency diagnostics rather than silent overwrite.
- Explicit image copies respect the source ownership boundary; external references remain shared when retained by the workflow. Saving values/reference metadata does not rewrite image pixels.
- Supported texture/vector authoring controls for eligible framework roles, plus expanded background, icon, marker, warning and cursor settings.
- Compact linked-value/Override rows; Scrollbars and Status Colours precede Tooltips. Source reading follows actual configured imports and authored expressions.
- Settings forms and editor styling
- Shared themed form-card/header/body structure for tooltip, context-menu, window-behavior and theme settings.
- Native slider, input, popup and slide-toggle rules plus reusable text/form roles; component/state classes retain their required structure.
- Editor styling uses configured tokens and Unity-skin colors for Light/Dark editor presentation.
- Persistence and lifecycle
- Current window-data schema includes tab membership and snapping/docking preferences, with migration of supported legacy/unversioned data.
- Memory enablement remains controller-owned; theme selection and preference resets do not override it.
- Tooltip handling accounts for target detachment, pointer interaction, dragging and scene changes, with delayed layout measurement and supported fades.
- Artwork and compatibility boundaries
- Trusted VectorImage roles are enabled in the supported Unity 6.3+ environment through existing compatibility configuration.
- Cursor/developer image authoring and imported player images retain their raster restrictions. No player-supplied SVG/font/code loader or separate icon-set authoring system is implied.
- Demo and documentation
- Demo metadata and 2.0 highlights updated, including compact image previews and page-width-constrained layout.
- Completed the 12-page manual covering requirements/setup, windows, interactions, Studio, the existing Developer Extension example, player themes, Visual Scripting, stylesheet ownership, the class reference and troubleshooting.
- Added diagrams/screenshots and responsive website overview/feature rows, plus configured Asset Store and playable-demo links.
Fixed
- Checked context-menu artwork uses the selected theme's configured icon/tint roles rather than a global fallback/background override.
- Theme creation/copy/save preserves supported source ownership and original declaration scopes instead of silently flattening unrelated rules or duplicating a competing defaults store.
- Flyout opening/selection handling avoids the previous reorder/open-transition conflict; theme removal confirms the actual entry and leaves source files on disk.
- Long Studio headings and the New This Version content fit their intended containers rather than forcing horizontal expansion.
- Automatic portable preparation skips legacy entries and clears stale derived exports while retaining diagnostics for genuine 2.0 failures.
- Renamed ThemeData URLs in four Demo UXML files now use the correct path and asset-name fragment with stable GUID references.
- Removed the unsupported runtime :last-child section-spacing selector; normal section spacing remains.
- The supplied controller-styled panel permits a null theme reference and uses Unity's supported intentional-no-theme warning option. No named placeholder stylesheet is required, and developer-owned panel configuration is not replaced.
- Documented stale Visual Scripting node-library rebuilding for initial/relevant-update setup. No automatic cache purge, graph deletion or regeneration on every Play Mode entry is required.
1.5.0 New features Added Unit Testing support
- Added playmode unit testing support. To use the unit test open the the test runner window (Window/General/Test Runner) and select the 'WindowFramework.Tests' test suite.
- Updated tooltip display logic, fades should be much smoother now
- Update tooltip placement logic, tooltips should now be placed correctly
- Updated context menu display logic, fades should be much smoother now
- Updated context menu placement logic, context menus should now be placed correctly
- updated context menu to close when needed based on clicks while passing the click down to the new element.
- Updated event registration system to better manage memory and resource usage.
- Updated tooltip and context menu to use the new event registration system.
1.4.1 Minor bug fixes
- Fixed bug where the window frame controller would not properly update the window frame when the window was closed.
1.4.0 Verified to work with Unity 6.6
- Verified Unity 6.6 support
- Verified compatability with Netcode for Game Object Client and Host builds
- Additional documentation blocks
- Minor fixes to better support client-only builds.
1.3.5 More Assembly Definition Tweeks
- Adjusted the build targets to be limited to client type builds only. If you want to use the windowing system on a server build you will have to adjust this.
1.3.1 Assembly Definition Files and Simpler Addressables Integration
- Verified to work with Unity 6.5
- Added Assembly definition files to better isolate code. This will allow for more integration in future releases.
- Addressables will now automatically be detected when installed (v2.9.0 or better), and the menu items will then become available.
- Activating Addressables support still requires that the Labels be set using the Addressables menu in the Theme Manager Window.
1.3.0 Addressables Support and Updated Documentation
- Themes can now use Addressables, this can be activated in the theme manager under the 'Addressables' menu item.
- Addressables support is a new feature in this asset and will be refined over time.
- You can assign which datafile is used as the Addressables item on the DataFile List of the Theme manager window.
- Form elements now use Player Prefs for settings. This includes Tooltip and Context menu settings. This change separates the controller from the form elements.
- Updated several documentation areas to remove outdated examples and better clarify existing ones.
- Tool tips will now automatically be applied to elements when using WindowFrameController.AddElement() to add UI content.
- Windows should no longer open off screen on load. This was caused when the screen size was changed while the WindowFrame controller is unavailable.
Side Note: Some people (including myself) have had issues opening UXML documents after upgrading to 6.4.0f1 If you have this problem opening the included UXML documents after upgrading to Unity 6.4.0f1 follow these steps:
- Close the project
- Open the Library folder in your file manager
- Delete the UiBuilder and UIElements folders
- Reopen the project and UI Builder should work again.
This will cause Unity to reimport the UIBuilder and related files
1.2.5 Minor fixes for deprecated calls
- Fixed some minor warnings of deprecated code on unity versions 6.3 and newer
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.
- Code organization in prep for future updates
- Fixed possable tooltip error when using multiple UI documents and scenes
- Starting on additional theme examples and theme manager additions, initial changes in the 6.3 theme include sliders, buttons, toggles and dropdowns. Any feedback on desired theme additions or changes would be apreciated.
- Verified compatability with Unity 6.4 beta
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.
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.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.