Change Details

minimally functioning toolbar fix auto hide toolbars in mobile correct resizing of the toolbar almost full functionality concept of currentHeader use only one global ApplicationHeader merge toolbars when there are both global and page ones try to dynamically load ToolBarPageHeader PrivateActionToolButton sizing on themes != desktop globalToolBar exported in api integrate with ActionButton fully support legacy more documentation proper page support dynamically changing the toolbar style correct layout for the global menu button better centering of breadcrumb tweak visible property move the global toolbar in own file add missing file work a bit better with layers start moving the globaltoolbar in the Page itself support rightReservedSpace warnings -- some RTL fixes fixes in toolbar sizing fix positioning of the handle fix none toolbar fix toolbar resizing behaviors focus the page on click ome preparations for custom headers export handleAnchor warnings-- fix top bar sizing menu don't animate top bar opacity add new files to qrc

The recomended toolbar to be used for kirigami applications used to need to be explicitly instantiated, and had an internal flickable that tried hard to be synchronized with the main PageRow. but this is pretty much impossible to have it glitch-free, it will there always be an edge case in which the two flickables gets out of sync, which is a strong sign of bad architecture. Page toolbars are now moved on top of Page itself, so on the same Flickable as the PageRow itself. (a global header is still used when we are in breadcrumbs mode) Is now also now possible to have multiple instances of PageRows, each one with its own globalToolBar. So, it's now also possible for AbstractApplicationHeader (and any subclass) to trach a different PageRow than the global one in ApplicationWindow. also, there have been requests to be possible while keeping the default toolbar, have a custom global one that goes on top of it (ApplicationWindow's header item) also, i wanted to have a way to make it possible to switch on the fly between a mobile-like and a desktop-like toolbar for further convergence plans in the future, it will be possible for pages to put their own component to replace the default toolbar

minimally functioning toolbar fix auto hide toolbars in mobile correct resizing of the toolbar almost full functionality concept of currentHeader use only one global ApplicationHeader merge toolbars when there are both global and page ones try to dynamically load ToolBarPageHeader PrivateActionToolButton sizing on themes != desktop globalToolBar exported in api integrate with ActionButton fully support legacy more documentation proper page support dynamically changing the toolbar style correct layout for the global menu button better centering of breadcrumb tweak visible property move the global toolbar in own file add missing file work a bit better with layers start moving the globaltoolbar in the Page itself support rightReservedSpace warnings -- some RTL fixes fixes in toolbar sizing fix positioning of the handle fix none toolbar fix toolbar resizing behaviors focus the page on click ome preparations for custom headersThe recomended toolbar to be used for kirigami applications used to need to be explicitly instantiated, and had an internal flickable that tried hard to be synchronized with the main PageRow. but this is pretty much impossible to have it glitch-free, it will there always be an edge case in which the two flickables gets out of sync, which is a strong sign of bad architecture. export handleAnchor warnings--Page toolbars are now moved on top of Page itself, so on the same Flickable as the PageRow itself. (a global header is still used when we are in breadcrumbs mode) Is now also now possible to have multiple instances of PageRows, each one with its own globalToolBar. So, it's now also possible for AbstractApplicationHeader (and any subclass) to trach a different PageRow than the global one in ApplicationWindow. fix top bar sizing menualso, there have been requests to be possible while keeping the default toolbar, have a custom global one that goes on top of it (ApplicationWindow's header item) don't animate top bar opacityalso, i wanted to have a way to make it possible to switch on the fly between a mobile-like and a desktop-like toolbar for further convergence plans add new files to qrcin the future, it will be possible for pages to put their own component to replace the default toolbar