Description: Forms in "Print" layout are automatically switching to "Web" layout whenever they are edited. Forms, even ones that are not being edited, in "Web" layout automatically switch to "Print" layout when you select print. Reproduction: Print -> Web 1) Create or open a form for editing (right-click the form then select edit) 2) Ensure the form is in "Print Layout" by selecting View->Print Layout. 3) Save the form. 4) Edit the form. The layout automatically changes to "Web", not honoring the layout it was in when it was last saved. In this case the desired behaviour is for the form, when edited, to open in the last mode it was saved it. This mode is obviously preserved, because when it's opened not for editing, it works correctly. Web -> Print 1) Create or open a form for editing. 2) Ensure the form is in "Web Layout" by selecting View->Web Layout 3) Save the form. 4) Run the form (double-click on it rather than editing) 5) Select File->Print. The layout automatically changes to "Print" layout and you cannot change it back without closing the form and reopening it. In this case the desired behaviour for a form that is not opened for editing is to either have the layout not be changed, or for the layout to return to what it was prior to printing. Discussion: Sometime in the 3.6 series, the decision was made that "Web" layout was going to be the default layout for Base forms. While in most cases this is probably appropriate, the way it was implemented was done without thinking through the consequences. First of all, the implementation switches all forms from "Print" to "Web" layout any time they are edited. This must be then manually reversed before the form is edited and saved. Secondly, when a form is being run and not edited, the layout options are disabled. However you can still, of course, select File->Print. When printing the form, the layout automatically changes to "Print". This cannot be changed back because those options are disabled. If changing the whole visual layout to "Print" is required before LO can actually print, then it should be reverted to what it was before it was printed after it's complete.
Lionel - thoughts? Sorry for bugging you on these UNCONFIRMED, I think we need a database QA expert also :-/
Reproduced in my libreoffice-3-6 and libreoffice-4-0 development builds. I didn't consider that print layout makes much sense for forms, since they are note designed to be printed, but used on screen. Web layout, which is more like 'screen layout' (that is, adjust to size of window dynamically instead of being fixed on a "paper size") makes more sense. However, if someone finds use in a print layout for forms, I'm not opposed to allowing it. As such, my opinions are: - The issue of the form switching to Print layout and being stuck there after "File / Print" is a genuine bug. However, it is not specific to forms; the same happens with a vanilla Writer document. - We need to be consistent on whether we allow print layout for forms or not. If we don't allow it, the "view / (web|print) layout" menu entries should be greyed out *both* in design mode (edit mode) *and* in normal mode. If we do allow it, then the "view / (web|print) layout" should be enabled *both* in design mode (edit mode) *and* in normal mode. The default when creating a new form should be Web layout.
For what it's worth, I find print layout quite handy for forms simply for the fact that many forms I design specifically to be able to be printed, and I like to lay them out on a page nicely. In a shameless plug that is beyond the scope of this bug, I'll say that I would personally find it far more useful for forms, when they are "run", to have their editing toolbars removed in order to maximize screen real estate. I can't emphasize enough how many times I've wished window size and toolbar layout could be specified on a per-form basis.
On pc Debian x86-64 with master sources updated yesterday, I could reproduce the bug. I noticed these logs: warn:legacy.osl:5151:1:xmloff/source/forms/propertyexport.cxx:595: OPropertyExport::implConvertAny: unsupported value type! warn:legacy.osl:5151:1:xmloff/source/forms/propertyexport.cxx:595: OPropertyExport::implConvertAny: unsupported value type! warn:legacy.osl:5151:1:xmloff/source/forms/propertyexport.cxx:595: OPropertyExport::implConvertAny: unsupported value type! warn:legacy.osl:5151:1:xmloff/source/forms/propertyexport.cxx:595: OPropertyExport::implConvertAny: unsupported value type! warn:legacy.osl:5151:1:xmloff/source/forms/propertyexport.cxx:595: OPropertyExport::implConvertAny: unsupported value type! warn:legacy.osl:5151:1:xmloff/source/forms/propertyexport.cxx:595: OPropertyExport::implConvertAny: unsupported value type! warn:xmloff:5151:1:xmloff/source/draw/shapeexport.cxx:558: com.sun.star.drawing.ControlShape
Adding self to CC if not already on
** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
I can only confirm the "Print -> Web" steps. "Print Layout" is now named "Normal". Version: 6.2.0.0.alpha1+ Build ID: fff34169fa912ad5096f1652172ea2455e5cb4d3 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: threaded from today
Dear Kurt, 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
Dear Kurt, 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