Since 2019 GSOC project it's possible to customize NB. There is an gui for it in Tools -> customize -> Notebookbar tab. It work that way that if you customize the NB the origin notebookbar.ui file will be copied to the user directory where than the visibility can be switched from true to false and the other way around. Since an glade update visibile=true was removed and now if there is no visibility=true property LibreOffice define it as visible=true. However as the GSOC student switch the visibility property it's not possible to switch true/false cause every time I update the NB with glade all visible=true will be removed. So would it be possible to update the gsoc code that if there is no property the customize dialog ADD visible=false to the ui file. I already asked the gsoc student. I'd like to update the notebookbar.ui files for better customization, but this is only usefull if this bug is fixed first, otherwise I will destroy the nb.ui file every time I edit it with glade.
code example notebookbar.ui file from writer: <object class="GtkToolButton" id="File-ExportToPDF"> <property name="visible">True</property> <property name="can_focus">False</property> <property name="action_name">.uno:ExportToPDF</property> <property name="use_underline">True</property> </object> If you open the file with glade, it change the property to <object class="GtkToolButton" id="File-ExportToPDF"> <property name="can_focus">False</property> <property name="action_name">.uno:ExportToPDF</property> <property name="use_underline">True</property> </object> and than it can't be edited with Tools -> customize -> Notebookbar tab. The command is visible in the gui you can edit the visibility checkbox, but in the code no new file was generated. I think it's cause the customization code do something like change visible property from True to False but as there is no visible property it didn't work.
I switch the importance, cause I can't work on notebookbar improvements (or bugfixes) without fix this bug.
I counseled against storing the .uis in the configuration like that. https://lists.freedesktop.org/archives/libreoffice/2019-May/082758.html
(In reply to Caolán McNamara from comment #3) > I counseled against storing the .uis in the configuration like that. > https://lists.freedesktop.org/archives/libreoffice/2019-May/082758.html In the configuration we store only pair <widget id>: <visibility true/false>. Then we use original .ui file and we generate new one in user directory with applied modifications from saved configuration. So we almost copy the file and only change some <property name="visible"> xxx </property> values.
and posibility we can fix it anyway?
Created attachment 163837 [details] Uwu
(In reply to andreas_k from comment #5) > and posibility we can fix it anyway? Heiko ?
(In reply to Xisco Faulí from comment #7) > (In reply to andreas_k from comment #5) > > and posibility we can fix it anyway? > > Heiko ? I'm afraid not me. But NEW, it's a regression IIUC.
I can't edit notebookbar files with glade and within the customize dialogue in LibO when this bug didn't get fixed.
There are many issue like this. QA upotes the importance transparently based on people on CC, dependencies, and see-also tickets.
No problem it block only my work on notebookbars. Compare to other bugs where there is only one bug related this bug is related to more than one bug. However.
Dear andreas_k, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug