[Bug 159380] close all (documents / windows) Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=159380 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159380] close all (documents / windows) Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=159380 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159380] close all (documents / windows) Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=159380 --- Comment #7 from peter josvai --- (In reply to Stéphane Guillou (stragu) from comment #5) > Thanks for clarifying. > On which operating system are you? Because how the Start Center and > components behave might differ slightly. > > (In reply to peter josvai from comment #3) > > and you couldn't get there otherwise, but by exiting, opening, and closing > > the blank document :) :) > It should be possible to open directly the Start Center (the grey document > icon in your applications), no need to create a new document then close it. > > UX/Design team, thoughts on a "close all documents and open start center" > command? > I think that, once more, this fits into your original request in bug 117237. > If we are able to keep track of a group of documents aka a "session", we > should also be able to close them all at once. I'm on Linux, Debian based... Star Center cannot be accessed via the grey icon, unfortunately.. (I've checked it on 2 machines) But the point, I believe, is not getting to the Start Center... but to handle groups of documents as sessions... Per program module, i.e. Writer (Heiko)... Start Center is just a device which could lead to sessions... Closing documents at once could lead to grouping them in the recent documents list... by two separators... which could be the start of something, still... But all roads seem to slope toward Sessions, somehow :) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 33603] Presenter notes should be available in normal view as a scrolling pane
https://bugs.documentfoundation.org/show_bug.cgi?id=33603 --- Comment #52 from Jeff Fortin Tam --- A more significant detail question: peeking at the commits, it is not entirely clear for me whether the current implementation also offers it as a sidebar by default (like in the mockup from attachment #154370) rather than only a bottom pane? As I originally wrote back in 2011, and I believe this is even more true today, using a sidebar for this rather than a bottom pane would make more sense as the default UX. Short summary of my reasoning: * Wide (& even ultrawide) landscape monitors have become the norm since the late 2000's * Screen-wide line lengths* are typographically hard to read, vs wrapping 45-75 cols * Presenter notes are often bullet-point form, i.e. lots of line breaks *: https://en.wikipedia.org/wiki/Line_length talks about the research Additionally, maybe the sidebar and bottom panel notes widget could have a button to toggle/switch between the two layout modes, for convenience. The app should then remember what the last chosen layout was. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 33603] Presenter notes should be available in normal view as a scrolling pane
https://bugs.documentfoundation.org/show_bug.cgi?id=33603 --- Comment #51 from Jeff Fortin Tam --- This is a minor UX detail, but based on what I see in Heiko's screenshot: please give the notes textfield a little bit of inner padding (a typical/standard value would be 6px), as the text (in the dark zone) being completely flush to the edge (before the light-gray zone) feels cramped and broken (a bit like bug #159531). -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 --- Comment #10 from Mike Kaganski --- (In reply to Rafael Lima from comment #9) I suggest even do it without saving all the unsaved changes ;-P -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159997] Request for Accounting Types of Number (Data)
https://bugs.documentfoundation.org/show_bug.cgi?id=159997 Heiko Tietze changed: What|Removed |Added CC||er...@redhat.com, ||libreoffice-ux-advise@lists ||.freedesktop.org Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Heiko Tietze --- Sounds minor but probably makes reading the data much easier. Difference is illustrated here https://support.microsoft.com/en-au/office/format-numbers-as-currency-0a03bb38-1a07-458d-9e30-2b54366bc7a4#__toc305071612 What do you think, Eike? Wait a second, it's a duplicate... *** This bug has been marked as a duplicate of bug 63536 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 --- Comment #9 from Rafael Lima --- What about we simply reload all opened files right after the security options are changed? This would be invisible to the user and would make the macros work. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 --- Comment #8 from Heiko Tietze --- Prototype could be Firefox's “Warning: Potential Security Risk Ahead” bypass [1], which an admin can disable [2] in the expert options. [1] https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean [2] https://medium.com/volosoft/how-to-disable-firefox-warning-potential-security-risk-ahead-f081fbf81a4f -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 --- Comment #7 from Mike Kaganski --- (In reply to Heiko Tietze from comment #6) > We better allow to execute the macro anyway. It is not an option. An admin could disallow users; and then the dialog would not allow changing the level, but your "allow to execute the macro anyway" would be a backdoor. > Adding more explanations, eg. what executing a macro means No one suggested to explain "what executing a macro means" up to now, it seems. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 133542] Pressing CTRL+W with a single document open closes LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=133542 Heiko Tietze changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9380 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159380] close all (documents / windows) Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=159380 Heiko Tietze changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||3542 --- Comment #6 from Heiko Tietze --- I wonder is all means all or just all from the current module, ie. Writer. Related is bug 133542 "Pressing CTRL+W with a single document open closes LibreOffice" rejected as CloseWin behaves differently from CloseDoc. Some wisdom in bug 85978 comment 15 (File > New is not the same as Window > New). Binding the close all function to the session idea is interesting. But then you cannot close all (random) documents. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159985] Changing Macro Security level should warn about the need to reload the file to apply the settings
https://bugs.documentfoundation.org/show_bug.cgi?id=159985 --- Comment #6 from Heiko Tietze --- I dislike the concept of changing a security level to once run an action. We better allow to execute the macro anyway. The confusion comes from the fact that most options are applied to the document. The function here is "Adjust the security level for executing macros and specify trusted macro developers.". Adding more explanations, eg. what executing a macro means, is not an improvement, IMO. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 33603] Presenter notes should be available in normal view as a scrolling pane
https://bugs.documentfoundation.org/show_bug.cgi?id=33603 Heiko Tietze changed: What|Removed |Added Keywords||needsUXEval -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 33603] Presenter notes should be available in normal view as a scrolling pane
https://bugs.documentfoundation.org/show_bug.cgi?id=33603 --- Comment #50 from Heiko Tietze --- Created attachment 192937 --> https://bugs.documentfoundation.org/attachment.cgi?id=192937&action=edit Screenshot (In reply to Sarper Akdemir (allotropia) from comment #49) > UX/Design team: I'd appreciate some additional opinions about the behavior > and current state. How would you like to see this notes panel end up? As Gabor pointed out users expect the common interactions. The context menu must not be the only way to format but an alternative to shortcuts (no ctrl+B to make the font bold yet, for example) and toolbar/sidebar/menu. The Properties sidebar deck changes however from editing to master attributes, I guess not only to avoid another deck but also for convenience since it's not possible to make the whole slide bold, for example. The only way out of the dilemma is to add the notes panel to the contextual presentation of the deck. And treat the notes panel like any other editing control, ie. the same context menus and the same interactions. Or to have zero formatting in the notes panel. But I think this wont be accepted either. (In reply to Gabor Kelemen (allotropia) from comment #47) > 1. Text formatting does not work... > 2. Pasting text from browser ...resizes font to an unreadably small size > 4. List formatting from sidebar in main view works > 5. Paragraph horizontal alignment formatting works > 6. Paragraph "distance after" seems to be much larger… Confirmed > 3. Area fill setting does not work Font color is not set automatically (remains white on yellow) > 7. The downwards pointing arrow does not change... Not confirmed (kf5, Karasa Jaga icon theme) -- You are receiving this mail because: You are on the CC list for the bug.
