Normally, if you change an attribute in a form using the control properties dialog box, the save icon will change its appearance as soon as you click into another attribute, adding the green "star" indicating that there has been a change. This does not happen for the width and height fields. As a consequence, there is no prompt to save the changes when the form document is closed, and the change is lost. I have tested this with a text box, a formatted field and an Image control. In my tests I have found no other attribute whith the same behaviour as for these two fields. The bug may be older than it seems: in 5.2 all seems to work properly, but this may be due to the fact, that the Save icon already shows the green star when opening the form document for editing, prompting to save the document even though you changed nothing. Thus the bug, if already present, would have been hidden.
+1 when using the properties dialog with a stand-alone document. Works as expected with the mouse. Caveat: editing an embedded database form in design mode, the form document is always dirty (modified) even when you did not change anything.
To avoid misunderstandings I wish to make my statement more precise. It seems that the fact that the form document is "dirty (modified)", as Andreas said, i.e. it is flagged as modified when looking at the save symbol, is somewhat dependent on the version and/or the operating system: it does not appear for me with Windows 10 & LibO 5.3.4.2, but it does appear, as I am told, for LO 5.4.1.2, with OpenSUSE 64bit, and obviously also for Andreas. But this is not crucial: Simply save the form document, if the flag appears after opening it for editing, and then start the operation as described. Mark well: You can save the document, using the save symbol as well as the menu entry, and the change is saved. The problem is that the flag is not set and therefore no prompt appears when closing the document. A second point I wish to make clear: the flag appears if you change width or height using the mouse; the wrong behaviour only happens when using the dialog fields for width or height. Another point, not connected with this bug, but important for the handling: In order to make a change in most dialog fields effective (a selection of a list box entry works differently, for example), you have to click elsewhere: into another field or outside of the dialog, to fire the event that sets the flag. I described this a bit more detailed in Comment #15 to Bug 103575.
Could confirm this buggy behavior. Changing of height and width of any field in a form by the properties of the control doesn't set the form to modified. Works when changing with mouse, fails with keyboard.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The problem ist still present in Version: 6.2.0.0.alpha0+ (x64) Build ID: 7119184f4b5441600f7b3eae7ec6771c094bbb7f CPU threads: 4; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-07-23_05:38:07 Locale: de-DE (de_DE); Calc: CL
Dear Gerhard Weydt, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The problem ist still present in Version: 6.3.1.2 (x64) Build-ID: b79626edf0065ac373bd1df5c28bd630b4424273 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
Dear Gerhard Weydt, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Created attachment 175484 [details] Test doc to show the bug I've added a very simple test document now to test the buggy behaviour. The bug persists in Version: 7.2.2.1 (x64) / LibreOffice Community Build ID: 0e408af0b27894d652a87aa5f21fe17bf058124c CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: threaded And here is the description of the steps to reproduce it: - Open the test document - Open the only form "Tabelle 1" for editing - As has been remarked before, the document will be automatically set to "changed" state, which will obscure the effect to be shown; hence save the form document. - Right-click the field with label "only field" and choose "Control Options" - Change width or Height fields and click into another field: the Save icon won't change state. - Then change another attribute, e. g. PositionX, and click into another field: the Save icon will change state. Expected behaviour is that the Save icon will change state also when width or height are changed.
Dear Gerhard Weydt, 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
Bug still exists in LO 7.6.2.1 on OpenSUSE 15.4 64bit rpm Linux.