[Libreoffice-ux-advise] [Bug 137160] ALPHABETICAL INDEX: need to add thin space between page reference and f./ff.
https://bugs.documentfoundation.org/show_bug.cgi?id=137160 Dieter changed: What|Removed |Added Keywords||needsUXEval Blocks||129434, 89606 Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from Dieter --- Thia is the question, if LO follows a certain style (could also be CMOS and some others). Unfortunately there is no internal guideline for that. I still think, at least Design-Team needs an internal consensus about it. cc: Design-Team for further input and decision Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=89606 [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=129434 [Bug 129434] [META] Writer (EDITING) Suggested bug fixes, enhancements and features for authors. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139302] [UI] Demote Chapter in navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=139302 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org, ||rayk...@gmail.com --- Comment #3 from Dieter --- cc: Design-Team cc: Jim Raykowski -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 --- Comment #13 from Mike Kaganski --- (In reply to V Stuart Foote from comment #12) > Ouch, that was a little too harsh Mike Indeed. If only Telesto could accept that when they do not understand an answer, that means a need to learn something, not keep insisting on own PoV along with stating own right to keep ignorant. It's OK when casual user gets confused with how to use bug tracker, and also how to interact when the problem is discussed; but when a #1 bug filer keeps showing the same inappropriate attitude, it's ... inappropriate. (In reply to Telesto from comment #10) > 16.30.2 appears to > be about 'Paragraph Styles (styles!). And text style referencing to > "character style" (I guess) > > I'm talking about the relevance of "Paragraph *Direct Formatting*" next to > "Character *Direct Formatting* ". I'm not talking about "paragraph styles". See 3.15.3 : http://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part3-schema.html#element-office_automatic-styles for another technical description why description of styles is relevant to DF. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 138942] In the Navigator, show separate nodes for Headings and Outline levels
https://bugs.documentfoundation.org/show_bug.cgi?id=138942 --- Comment #4 from Jim Raykowski --- Sorry, I'm not quite following. An example document with a list of what is to be included in the "Outline" and "Headings" nodes may help. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139037] UI: collapsed pre-formatted text in style inspector keeps expanding after each cursor position change
https://bugs.documentfoundation.org/show_bug.cgi?id=139037 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 --- Comment #12 from V Stuart Foote --- (In reply to Mike Kaganski from comment #11) Ouch, that was a little too harsh Mike, but yes I would agree that some of Telesto's musings are not as well structured or researched as they should be. But he really does poke at some of the frayed edges of the UI--we have a spot for him here if he could perhaps edit his submissions. Stuart -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 --- Comment #11 from Mike Kaganski --- (In reply to Telesto from comment #10) > Ask LibreOffice is about user questions.. This ends up in the area of > technical questions. At ask people assume things to be this way. Or ask what > the practical issue is Or give quick fixes (workarounds). > > So it's misplaced at ask (if you ask me). No I do not ask you. Ask is for user questions; and this is a user question. Especially since it focuses on "usefulness", which is a topic exactly fit for Ask. And no, this is not technical question, since strictly correct and technical answer about *why* is it so is not good for you. > FWIW: Enhancement request are no bugs either, if we want be nitpicking. So > don't belong here. Would belong to UX enhancement request tracker or > whatever. Yet another unsolicited off-topic from you. Bugzilla is for what TDF intends it, not for what you imagine it is for. It is *the* place for enhancements. Period. > I'm surely not good at reading technical documentation. You surely are not. What you're good at is wasting everyone's time. > 16.30.2 appears to > be about 'Paragraph Styles (styles!). And text style referencing to > "character style" (I guess) Yes. Styles, as defined by ODF, and in ODF, *every* bit of formatting is implemented using styles, DF being defined also by special kind of styles - automatic styles. So everything described in 16.30.2 applies to DF. > The advantage of the (presence of) Paragraph Direct Formatting next to > Character Direct Formatting being unclear to me. This is definitely off-topic here. As said, "what is it useful for" is for Ask, whatever you might think. > > Direct Formatting should not be be distributed around easily. It should be > reduced to a minimum (without breaking user experience using DF) to make > working with style a success, IMHO. > And distinctions between Paragraph Direct Formatting/ Character Direct > Formatting kind of subtle (without being visible; making managing even > harder. You easy distributing DF all over the document without knowing. > Ruining the user experience of using (paragraph) styles. You need to > manually scrub all DF. Polluting the XML files with unnecessary (additional) > DF junk. More unrelated stuff. Not surprising. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 --- Comment #10 from Telesto --- (In reply to Mike Kaganski from comment #9) > (In reply to Telesto from comment #7) > > But is indeed not the 'fault' of the style inspector. It's only making some > > of internal clear.. I didn't even realized existed.. > > > > But core is indeed not about the style inspector > > Heh, so it looks like the reopening was just because you misuse Bugzilla to > be your place to ask "what-is-it and how-to-use" questions? Indeed, this > confirms this: > > (In reply to Telesto from comment #5) > > More intended as an inquiry.. of naïve asking what the idea behind the > > concept is.. Not to get comment 0 through. > > > > That I report it as a 'bug' doesn't necessary mean it's bug. Except I tend > > to perceive it as bug 'initially; . > > We have Ask LibreOffice for questions. Please use the right tool. Ask LibreOffice is about user questions.. This ends up in the area of technical questions. At ask people assume things to be this way. Or ask what the practical issue is Or give quick fixes (workarounds). So it's misplaced at ask (if you ask me). You could argue it's misplaced here too as it start with more or less technical inquiry. I unintentionally saw it a issue fixating on Style Inspector, which was wrong (as Baron pointed out) So this in my opinion not a true ask question. More a possible 'bug'/ enhancement. FWIW: Enhancement request are no bugs either, if we want be nitpicking. So don't belong here. Would belong to UX enhancement request tracker or whatever. The inquiry based on: "So someone who does not understand the difference, and actually has no actual problem with it, tries to "simplify" things they don't understand?" It's surely possible I don't understand. Happily to admit. Except, the way you tend to present it, makes it look like rather obvious, while refrain from explaining it (in my perception). > See "16.30.2 Paragraph Styles" in ODF [1]: > > > In addition to paragraph properties, paragraph styles may define text > > properties. These are applied to the character content of the paragraph > > unless they are overwritten by a text style that is specified by any of > > the descendant elements of the paragraph element. > > [1] > http://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part3- > schema.html#__RefHeading__1416408_253892949 I'm surely not good at reading technical documentation. 16.30.2 appears to be about 'Paragraph Styles (styles!). And text style referencing to "character style" (I guess) I'm talking about the relevance of "Paragraph *Direct Formatting*" next to "Character *Direct Formatting* ". I'm not talking about "paragraph styles". And even if the documentation opens the possibility still doesn't explain the need of usefulness, IMHO The advantage of the (presence of) Paragraph Direct Formatting next to Character Direct Formatting being unclear to me. Direct Formatting should not be be distributed around easily. It should be reduced to a minimum (without breaking user experience using DF) to make working with style a success, IMHO. And distinctions between Paragraph Direct Formatting/ Character Direct Formatting kind of subtle (without being visible; making managing even harder. You easy distributing DF all over the document without knowing. Ruining the user experience of using (paragraph) styles. You need to manually scrub all DF. Polluting the XML files with unnecessary (additional) DF junk. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139351] proposal for Paste Special Sticky
https://bugs.documentfoundation.org/show_bug.cgi?id=139351 --- Comment #8 from Robert Lacroix --- (In reply to Heiko Tietze from comment #7) > Don't see this going to fly. We are restricted to the open document format > and cannot bind any property to cells. My take => WF. > > Plus, regular copy/paste interactions really sounds like a job for functions. Ironically, ODF explictly allows implementation-dependent content. Furthermore, XML inherently allows extensions to a schema; a document processor should preserve original content not defined in the schema. Something to look into in LO. Anyway - something I agree with - a collection of sticky properties (grouped as a style) would be more useful than the general case of every cell having an independent set of sticky properties. It would require the implementation of Paste Special Sticky to look at the style attached to a cell to see what is permissible to copy. Would that fly? 3.1.1 General OpenDocument defines two methods of document representation: •A single XML document. •A collection of files within a package ([ODF1.3-Part-2:Packages]), each of which stores a part of a complete document. ... A package may also contain image files, embedded objects and implementation-dependent files. https://docs.oasis-open.org/office/OpenDocument/v1.3/cs02/part3-schema/OpenDocument-v1.3-cs02-part3-schema.html -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139330] UI is unfriendly, opening a new layer instead of the last one when the layer tab list is full
https://bugs.documentfoundation.org/show_bug.cgi?id=139330 Heiko Tietze changed: What|Removed |Added Blocks||99648 Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE Severity|minor |enhancement --- Comment #6 from Heiko Tietze --- Tabs have its limitations. Would prefer a solution per Navigator as suggested here [1] and resolve this ticket as duplicate of bug 56498 (having more people on CC/tickets in duplicates raises the importance). Please reopen if you disagree. [1] https://design.blog.documentfoundation.org/2016/07/31/how-the-navigator-may-support-object-handling-in-libreoffice-draw/ *** This bug has been marked as a duplicate of bug 56498 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99648 [Bug 99648] [META] Improve Layer Handling -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 134554] [META] Styles Inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=134554 Bug 134554 depends on bug 139338, which changed state. Bug 139338 Summary: The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless https://bugs.documentfoundation.org/show_bug.cgi?id=139338 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 Mike Kaganski changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #9 from Mike Kaganski --- (In reply to Telesto from comment #7) > But is indeed not the 'fault' of the style inspector. It's only making some > of internal clear.. I didn't even realized existed.. > > But core is indeed not about the style inspector Heh, so it looks like the reopening was just because you misuse Bugzilla to be your place to ask "what-is-it and how-to-use" questions? Indeed, this confirms this: (In reply to Telesto from comment #5) > More intended as an inquiry.. of naïve asking what the idea behind the > concept is.. Not to get comment 0 through. > > That I report it as a 'bug' doesn't necessary mean it's bug. Except I tend > to perceive it as bug 'initially; . We have Ask LibreOffice for questions. Please use the right tool. See "16.30.2 Paragraph Styles" in ODF [1]: > In addition to paragraph properties, paragraph styles may define text > properties. These are applied to the character content of the paragraph > unless they are overwritten by a text style that is specified by any of > the descendant elements of the paragraph element. [1] http://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part3-schema.html#__RefHeading__1416408_253892949 -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 61835] WRITER TABLE: Let user drag the border of a table column while keeping the other columns intact (workaround in comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=61835 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | Severity|minor |enhancement CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||mentoring@documentfoundatio ||n.org --- Comment #12 from Heiko Tietze --- (In reply to Dieter from comment #11) > ... press the left or the right arrow key Don't see a reason why this shouldn't work with the mouse. The alt+arrow interaction is exactly what's expected for alt+left_mouse (which is used for window movement in KDE). Perhaps an easyhack. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 --- Comment #8 from Telesto --- (In reply to Aron Budea from comment #6) > This situation reminds me of changing a piece of text eg. to bold, then > changing back to regular. You won't see a difference, but it'll still have > direct formatting, regular, you have to clear the formatting for the text to > become unformatted. Bug 135871 being one of those (and Bug 135871 comment 22 listing even more) -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 --- Comment #7 from Telesto --- (In reply to Aron Budea from comment #6) > (In reply to Telesto from comment #5) > > And having to types of direct formatting is really hard get a grip on. As > > kind of invisible.. Yes, with style inspector it's visible.. but now I have > > having trouble avoiding certain effects. > This situation reminds me of changing a piece of text eg. to bold, then > changing back to regular. You won't see a difference, but it'll still have > direct formatting, regular, you have to clear the formatting for the text to > become unformatted. > Also, this whole discussion is completely unrelated to the Styles Inspector, > which just shows what exists in the document. You're right Aron.. I was kind of focused on Style Inspector, because being surprised by seeing Direct Formatting at Paragraph level.. Whereas I assumed this to be only happening at Character Level. And in a follow up found it pretty confusing having multiple DF settings set. Which not even 'match' reality. So you can have a paragraph with DF saying font X. Where its overwritten by DF Character Style for the full paragraph. But is indeed not the 'fault' of the style inspector. It's only making some of internal clear.. I didn't even realized existed.. But core is indeed not about the style inspector -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 --- Comment #6 from Aron Budea --- (In reply to Telesto from comment #5) > And having to types of direct formatting is really hard get a grip on. As > kind of invisible.. Yes, with style inspector it's visible.. but now I have > having trouble avoiding certain effects. This situation reminds me of changing a piece of text eg. to bold, then changing back to regular. You won't see a difference, but it'll still have direct formatting, regular, you have to clear the formatting for the text to become unformatted. Also, this whole discussion is completely unrelated to the Styles Inspector, which just shows what exists in the document. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 --- Comment #5 from Telesto --- (In reply to Mike Kaganski from comment #4) > (In reply to Telesto from comment #0) > > The distinction paragraph <-> Character direct formatting in style inspector > > seems a kind of pointless > > (In reply to Telesto from comment #3) > > And explain to me what I should make off it.. > > I'm sorry, is this a kind of "I don't understand what it is, so let's break > it" kind of request? So someone who does not understand the difference, and > actually has no actual problem with it, tries to "simplify" things they > don't understand? More intended as an inquiry.. of naïve asking what the idea behind the concept is.. Not to get comment 0 through. That I report it as a 'bug' doesn't necessary mean it's bug. Except I tend to perceive it as bug 'initially; . I don't not really get that it's possible to 'set a DF at paragraph level', which is overridden by Character DF formatting.. for the full paragraph depend how the formatting being changed.. So changing the font at the start is assumed to be DF paragraph style, but maybe it intended only to have say a Different type of font for the first letter? Or fist word.. And PS direct formatting obviously causes a lot of DF being present.. While styles a propagated. So maybe you only want to change DF at character level, and you get 'DF at paragraph level' And having to types of direct formatting is really hard get a grip on. As kind of invisible.. Yes, with style inspector it's visible.. but now I have having trouble avoiding certain effects. As hard as switching font from to something else, back to default doesn't mean.. back in line with 'style', but DF formatting font set. Which also hard to revert. [I my position is that shouldn't happen ideally in the first place] But maybe I change position what the idea behind Paragraph DF is. As it's not clear to me what purpose/advantage is next to DF at character level.. This might be 'sane' approach or having an advantage.. I can place it currently. Why this is needed/wanted. In relation to Character DF and in relation to using PS Styles. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139037] UI: collapsed pre-formatted text in style inspector keeps expanding after each cursor position change
https://bugs.documentfoundation.org/show_bug.cgi?id=139037 Heiko Tietze changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Heiko Tietze --- Putting the focus on another place change the formatting and must result in a rebuilt tree. And it's not guaranteed actually and rather unlikely that your next position has the same structure / hierarchy. Resolving as dup since the request is the same. *** This bug has been marked as a duplicate of bug 139361 *** -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139359] Inserting a symbol does insert lots of direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=139359 Heiko Tietze changed: What|Removed |Added Severity|normal |enhancement --- Comment #4 from Heiko Tietze --- We should avoid DF and use only if the font is different than what is used in the paragraph. Mike, what do you think? -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 134554] [META] Styles Inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=134554 Heiko Tietze changed: What|Removed |Added Depends on||139361 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139361 [Bug 139361] UI: Retrain manually set collapsed states in style inspector -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 134554] [META] Styles Inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=134554 Bug 134554 depends on bug 139361, which changed state. Bug 139361 Summary: UI: Retrain manually set collapsed states in style inspector https://bugs.documentfoundation.org/show_bug.cgi?id=139361 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139361] UI: Retrain manually set collapsed states in style inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=139361 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Blocks||134554 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | Resolution|--- |WONTFIX Severity|normal |enhancement --- Comment #3 from Heiko Tietze --- -1 from my side. While in general user settings should be remembered and the expansion state is often such a setting, it's not always and not in case of the SI. The purpose is to inspect text for some rare cases for own documents or more often if you receive buggy documents from different sources. But it's not to investigate just DF and to ignore other properties. Usually, the style modifies just a few attributes, which fits easily into the tree. So => WF Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=134554 [Bug 134554] [META] Styles Inspector -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139351] proposal for Paste Special Sticky
https://bugs.documentfoundation.org/show_bug.cgi?id=139351 --- Comment #7 from Heiko Tietze --- Don't see this going to fly. We are restricted to the open document format and cannot bind any property to cells. My take => WF. Plus, regular copy/paste interactions really sounds like a job for functions. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 --- Comment #4 from Mike Kaganski --- (In reply to Telesto from comment #0) > The distinction paragraph <-> Character direct formatting in style inspector > seems a kind of pointless (In reply to Telesto from comment #3) > And explain to me what I should make off it.. I'm sorry, is this a kind of "I don't understand what it is, so let's break it" kind of request? So someone who does not understand the difference, and actually has no actual problem with it, tries to "simplify" things they don't understand? -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139562] Add opportunity to delete all manual inserted Page breakes in Calc for one time
https://bugs.documentfoundation.org/show_bug.cgi?id=139562 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Keywords||needsUXEval Blocks||109110 CC||libreoffice-ux-advise@lists ||.freedesktop.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109110 [Bug 109110] [META] Calc page break issues -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139094] UI: Border selector still in selected state after clicking different border
https://bugs.documentfoundation.org/show_bug.cgi?id=139094 Telesto changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|UNCONFIRMED --- Comment #5 from Telesto --- Setting to UNCONFIRMED.. I know.. Bug tracker is not help.. but tend to see flakyness What's DontChange supposed to be of an state.. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 134554] [META] Styles Inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=134554 Bug 134554 depends on bug 139338, which changed state. Bug 139338 Summary: The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless https://bugs.documentfoundation.org/show_bug.cgi?id=139338 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 Telesto changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- --- Comment #3 from Telesto --- (In reply to Heiko Tietze from comment #1) > Absolutely not. Character properties are not set via direct paragraph > settings. Actually I don't see any overlapping. But if you merge the sources > how should a user learn where the attribute comes from? Please see screencast.. And explain to me what I should make off it.. Not sure how I get back to 'paragraph direct formatting' following comment 0 Setting to UNCONFORMED in for answer for now.. Could also set it NEEDINFO, but would be the opposite of what NEEDINFO means in normal cases. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 --- Comment #2 from Telesto --- Created attachment 168838 --> https://bugs.documentfoundation.org/attachment.cgi?id=168838=edit Screencast Still not totally clear what the meaning is of Paragraph Direct Formatting -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139341] The new "View > User Interface" dialog does not switch between the options properly
https://bugs.documentfoundation.org/show_bug.cgi?id=139341 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||3607 --- Comment #3 from Heiko Tietze --- Was going to agree with the separator between MUFFIN and classic UI variants. But in fact switching between the options keeps the customization. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 134554] [META] Styles Inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=134554 Heiko Tietze changed: What|Removed |Added Depends on||139338 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139338 [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139338] The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless
https://bugs.documentfoundation.org/show_bug.cgi?id=139338 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG Blocks||134554 --- Comment #1 from Heiko Tietze --- Absolutely not. Character properties are not set via direct paragraph settings. Actually I don't see any overlapping. But if you merge the sources how should a user learn where the attribute comes from? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=134554 [Bug 134554] [META] Styles Inspector -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 134554] [META] Styles Inspector
https://bugs.documentfoundation.org/show_bug.cgi?id=134554 Bug 134554 depends on bug 139338, which changed state. Bug 139338 Summary: The distinction paragraph <-> Character direct formatting in style inspector seems a kind of pointless https://bugs.documentfoundation.org/show_bug.cgi?id=139338 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139115] UI Change default behavior of treelist toggles with more than 1 checkbox
https://bugs.documentfoundation.org/show_bug.cgi?id=139115 --- Comment #3 from Jan-Marek Glogowski --- There is https://gerrit.libreoffice.org/c/core/+/108947 This reverts the default behavior to the previous state and adds an opt-in API used by the AutoFilter. It also has "toggle after select" implemented as a 3rd, yet unused option. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139331] Option to redact/ anonymizing file by replacing images by dummy or make them black (Sanitize media)
https://bugs.documentfoundation.org/show_bug.cgi?id=139331 Heiko Tietze changed: What|Removed |Added CC||muhammet.k...@collabora.com Severity|normal |enhancement --- Comment #2 from Heiko Tietze --- Muhammet, what do you think? -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 138247] Calc UI: Make the comment UI more consistent
https://bugs.documentfoundation.org/show_bug.cgi?id=138247 Heiko Tietze changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=83 ||575 -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 138247] Calc UI: Make the comment UI more consistent
https://bugs.documentfoundation.org/show_bug.cgi?id=138247 Heiko Tietze changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=73 ||446 Severity|normal |enhancement --- Comment #6 from Heiko Tietze --- Summary is a bit misleading. You don't seek for consistency with other modules but a) dislike the disappearing of empty comments and b) the way how comments are shown. For a) we have bug 73446 and bug 134825 (but see also 83575). If we keep empty comments you need to introduce a method to delete, for example per context menu- and many users will complain about the two additional clicks. Or per small close button on top right, which might annoy people with small screens. Regarding b) you run into the same trouble with this "large" comment button. And consider a large sheet with many comments where your big button significantly adds clutter. Or two adjacent cells with comments... But I agree with the issues. We could introduce options and make the application a it responsive where large screens show bigger controls. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 139115] UI Change default behavior of treelist toggles with more than 1 checkbox
https://bugs.documentfoundation.org/show_bug.cgi?id=139115 --- Comment #2 from Heiko Tietze --- I dislike those auto-check-on-row-click activation in general since it covers the selection mechanism. Bug 116675 talks about the missing checkbox label connection for a UI with apparently no columns. My take: if the checkbox has a label clicking this should toggle the state, whether in a table/tree or not. If the table/tree has one or many checkboxes with a label relation at another column we do not auto-toggle the first (or any other) checkbox. One has to explicitly click the checkbox. Exception might be when the table must not be used for selection, but no actual situation pops up where this would apply now. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
