<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED NOTABUG - Writer: Can't switch to Portrait" href="https://bugs.documentfoundation.org/show_bug.cgi?id=126608#c55">Comment # 55</a> on <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED NOTABUG - Writer: Can't switch to Portrait" href="https://bugs.documentfoundation.org/show_bug.cgi?id=126608">bug 126608</a> from <a class="email" href="mailto:ToddAndMargo@zoho.com" title="Todd <ToddAndMargo@zoho.com>"> Todd</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=126608#c51">comment #51</a>) > > Hmm, you've had four of the sharpest QA reviewers working on the project > tell you that you are incorrect. You've received precise examples and > explanations to enable you to perceive where your usage is not in line with > function. Yet you still claim there is a bug... at some point folks will > tell you to move on. Meanwhile the UX facet of why it causes issues is our > ongoing dichotomy of Direct Formatting vs. Style based authoring. That you for helping me make my point. All those sharp guys did not really help until Regina took a look. What they did was give me work arounds, which were appreciated but not the point of the bug report. It took Regina to hit pay dirt. So I guess five is the magic number. > Meanwhile examine the behavior of the Status bar indicator of the Page > style, it is context menu (i.e. r-mouse click) enabled to allow you to > select from the defined page styles and will display the Name of the page > style applied to the document page with text cursor focus. It does not give > any indication when the style has been modified from its template defaults. > Open <a href="http://bugs.documentfoundation.org/attachment.cgi?id=153099" name="attach_153099" title="sample document not using Default page template">attachment 153099</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=153099&action=edit" title="sample document not using Default page template">[details]</a>, its view mode should make the page styling > apparent. I do understand what you are saying. But from a users standpoint, you are tell him that up is down and down is up. Portrait is Landscape and Landscape is Portrait. This is a nightmare for the user. Do you expect the user to code directly in XML so he gets what he wants? The user expects the "Style" pop up to be the style of the current page and subsequent pages NOT THE WHOLE STINKING DOCUMENT. The Style pop up should create a new set of rules in a new or previously used style. Styles themselves are a great way of doing this, but your flow control of styles is what is in question, not the styles themselves. You have to look at this from the user's standpoint, not the developers. This bug report all started with me having to urgently send a customers a document with mixed Landscape (first page) and Portrait mixed together and I could not figure out how in the h*** I lost my ability to use Portrait (he accepted everything is Landscape, fortunately). And I am a YUGE fan of LO and a BS in comptuer engineering and an I.T. professional to boot AND even I could not figure it out. And googeling it was no use either. (I have since wrote up how to do it from myself.) How in the world would you expect a standard user to figure it out? This is why I can't get anyone to seriously adopt LO, even thought it is a great piece of software.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>