Bug 113828 - Add statusbar tab to customization dialog
Summary: Add statusbar tab to customization dialog
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.0.0.alpha1+
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 122834 145328 163089 163985 (view as bug list)
Depends on: 92406 112620
Blocks: Statusbar Customise-Dialog
  Show dependency treegraph
 
Reported: 2017-11-14 14:38 UTC by Yousuf Philips (jay) (retired)
Modified: 2025-11-21 13:01 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2017-11-14 14:38:20 UTC
The statusbar is an xml file similar to the toolbar xml files, and users want to be able to customize it to their needs by adding, removing and disabling features in it (e.g. bug 88296, bug 86303), so it would be good to have this feature added to the customization dialog.
Comment 1 Thomas Lendo 2017-11-14 20:39:06 UTC
I don't know if this is a good idea. On other issues I seem to remember that it's not wanted that the Statusbar is customizable.
Comment 2 Heiko Tietze 2017-12-19 09:48:35 UTC
Please consider access to macros as solution to bug 101576 that requests to show MAX(SELECTION)-MIN(SELECTION) at the status bar.
Comment 3 Maxim Monastirsky 2017-12-19 12:36:17 UTC
Makes sense, but not before Bug 112620 is solved, so we could filter all those toolbar/menu commands that don't apply to the status bar. (FYI sdi files used to have also a StatusBarConfig setting, but it was removed last year, because it was not used from the code - https://cgit.freedesktop.org/libreoffice/core/commit/?id=ccbed01b40c9bc4421943ebe1fe818d43aadcc7d).
Comment 4 Heiko Tietze 2021-11-08 09:15:59 UTC
*** Bug 145328 has been marked as a duplicate of this bug. ***
Comment 5 Heiko Tietze 2024-07-01 11:27:53 UTC
*** Bug 122834 has been marked as a duplicate of this bug. ***
Comment 6 Heiko Tietze 2024-09-23 09:21:31 UTC
*** Bug 163089 has been marked as a duplicate of this bug. ***
Comment 7 V Stuart Foote 2024-11-27 15:54:00 UTC
*** Bug 163985 has been marked as a duplicate of this bug. ***
Comment 8 Hartmut Schorrig 2025-11-20 10:42:40 UTC
As a normal, but sw-technical oriented user, I agree really to the origial requirement from Yousuf Philips in 2017-11-14.
But, ... the consideration should be, who (which person) should responsible to change the appearance of the status bar. If anybody can do it with very simple handling, then sometimes stupid things may be done, and afterwards questions and discussions are taken etc. The same may be also possible for the toolbar configuration: A normal user switches off an important entry, accendently with too less knowledge, and then ask "where is the entry". Are such cases evident?
That's why, according to my requirements and in my opinion, changing the appearance of the status bar may be sufficiently done by editing a plain text file in the 
.config/libreoffice/4/user/config/soffice.cfg/modules/swriter/statusbar/
directory. Means immediately in the XML file (better in a Yaml or such, or a plain text with simple syntax). Then only an expert for such dares to change something. And he/she sees by itself as responsible to proper working. 
But - I have looked in this directory, under Linux debian 12. It is empty. In opposite, in .../toolbar directory I see the XML file only with my changes (or the whole config, not exactly analyzed.
It means, if the given configuration is stored there, and removing one topic (for example the page style is not necessary for me) is successfull, then only the question remains, how to enter new entries. But this is a question of help for uno commands, possible for the expert. 
That would be a simple solution with not too much effort for this feature request.
I understand and agree, that introducing a complex UI-handling to change the status bar with inside LibreOffice is a greater challenge, not simple to solve for all considerations and user types.
Comment 9 Yousuf Philips (jay) (retired) 2025-11-21 13:01:11 UTC
The design team has made a mockup ( attachment 192719 [details] ) in bug 92406.