https://bugs.documentfoundation.org/show_bug.cgi?id=92406
--- Comment #27 from Freddy J <[email protected]> --- (In reply to V Stuart Foote from comment #23) > (In reply to Eyal Rozenberg from comment #22) > > > > > 1. The status bar is a kind of toolbar, but a special special kind. > > True, but TB in that it can only be toggled shown or hidden. > > > 2. Some UNO entities can be placed on both regular toolbars and status > > (tool)bars, some only on regular toolbars, some only on status (tool)bars. > > Let's call the union of these three sets "toolbarable UNO entities". > > OK > > > 3. The question of which kinds of toolbar a bar entity can be placed on > > depends on whether developers have implemented a "regular toolbar mode" and > > a "status (tool)bar mode" for that entity. For example, the "Save" entity > > has both modes implemented and can be placed either on a regular toolbar or > > the status bar. > > I guess, seem to recall the UNO for the status bar are unique, like the > Style and SideBar UNO. But we don't expose the Status Bar controls to the > Customize dialog. > > > 4. The same dialog is used for configuring all toolbars, including the > > status bar. > > OK, currently there is no UI to configure the Status Bar; but could be the > same as the groupings for Styles and SB. Would not need to be integrated. > > > > > What do you think? > > While a Toolbar from .UI perspective, the Status Bar is not currently > available to manipulate from the Customize dialog. > > But as Regina notes comment 15 the configuration XML for the Status Bar can > be directly adjusted: > > The statusbar.xml found on a recent nightly on Win10 > C:\LODev2480_20240219_TB77\share\config\soffice. > cfg\modules\swriter\statusbar\statusbar.xml > > The specific stanzas for the available UNO widgets [1] set a number of > parameters: align, autosize (if appropriate), mandatory (priority show as > bar is shrunk). All T/F binary, and also a configured width (integer). > > =-ref-= > [1] list of UNO widgets held on the Status TB in the default sequence: > .uno:ModifiedStatus > .uno:StatePageNumber > .uno:StateWordCount > .uno:StateAccessibilityCheck > .uno:PageStyleName > .uno:LanguageStatus > .uno:InsertMode ** > .uno:SelectionMode > .uno:Signature ** > .uno:Size > .uno:ViewLayout > .uno:ZoomSlider > .uno:Zoom > https://fivenightsatfreddys2.org > > ** an UNO command that can be assigned via Tools -> Customize other than to > Status Bar. A simple checkbox UI for toggling visibility, combined with the ability to mark items as mandatory, seems like the best balance between flexibility and usability. Full integration into the customization dialog would be ideal long-term, but a lightweight solution could deliver real value quickly. -- You are receiving this mail because: You are the assignee for the bug.
