<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - FILEOPEN: Read-only file is open with design mode enabled." href="https://bugs.documentfoundation.org/show_bug.cgi?id=114246#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - FILEOPEN: Read-only file is open with design mode enabled." href="https://bugs.documentfoundation.org/show_bug.cgi?id=114246">bug 114246</a> from <a class="email" href="mailto:lionel@mamane.lu" title="Lionel Elie Mamane <lionel@mamane.lu>"> Lionel Elie Mamane</a> <pre>For full clarity: The user needs to go _once_ in edit mode, configure the document to open forms in non-design mode, save the document, and from then on the "problem" is solved _forever_ for this document. Or do that at the same time he sets the document to open in read-only mode. Indeed, before 2014 my patch, read-only document had form design mode artificially forced to off. Since these are two orthogonal (independent) settings (and behaviours), it seems clearer and easier to me to understand what happens if they are kept orthogonal. Maybe that's too geeky a worldview, and I'll respect the UX's team opinion on that. *But* note that just reverting the relevant hunk from my patch (file svx/source/form/fmview.cxx method FmFormView::Init) will create problems for Base form documents (which are Writer documents embedded in an odb container). That is because Base form documents do _not_ have a switch to go to edit mode once they are in read-only mode _unless_ they are in "form design mode". So forcing form design mode to off in read-only mode leads to an inescapable situation where the form document can never be edited again. See <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - EDITING - A form set to open in read-only mode can never be switched back" href="show_bug.cgi?id=44081">bug 44081</a> for that. Maybe we could do it the other way round for Base form documents: ignore their read-only property when they are open in edit / form design mode. That could be workable and give another (quite natural) way out of the inescapable situation.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>