[Libreoffice-ux-advise] [Bug 148782] "Left frame border" and "Right frame border" options for Horizontal "to" position in Position and Size for shapes should be changed to "Left of frame text area" an
https://bugs.documentfoundation.org/show_bug.cgi?id=148782 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||148519 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148519 [Bug 148519] Change "Margin" to "Entire Frame" in "to" field for Vertical Position when anchoring "To frame" in Position and Shape tab -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148519] Change "Margin" to "Entire Frame" in "to" field for Vertical Position when anchoring "To frame" in Position and Shape tab
https://bugs.documentfoundation.org/show_bug.cgi?id=148519 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||148782 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148782 [Bug 148782] "Left frame border" and "Right frame border" options for Horizontal "to" position in Position and Size for shapes should be changed to "Left of frame text area" and "Right of frame text area" -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148782] "Left frame border" and "Right frame border" options for Horizontal "to" position in Position and Size for shapes should be changed to "Left of frame text area" an
https://bugs.documentfoundation.org/show_bug.cgi?id=148782 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||103270, 108741 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||rb.hensc...@t-online.de Keywords||needsUXEval Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103270 [Bug 103270] [META] Image/Picture dialog bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108741 [Bug 108741] [META] Shapes bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148464] Ability to pick-and-choose where to search
https://bugs.documentfoundation.org/show_bug.cgi?id=148464 --- Comment #4 from Eyal Rozenberg --- (In reply to Heiko Tietze from bug #96474 comment #10) > The topic was on the agenda of the design meeting. > > Solution a) is to list all entities similar to attributes and check it by > default. The idea in comment 3 is not flexible, hard to understand and takes > a lot of space. > Solution b) would be to know where the search was started from and allow to > "[ ] Search only in %1". > Solution c) is to start the search command with a parameter like > .uno:Search?where="comment" and allow to restrict the search to this entity > only > > Solutions b) and c) clutter less, a) is more flexible (but requires a check > all/none option). I'll rephrase, since the minutes mis-capture my opinion as it evolved over the course of the meeting.. (a) (b) and (c) are for me all parts of the same solution: * A sub-dialog of the F dialog will list all _kinds_ of entities, just like we currently have for Attributes. The entries could be something like: Body, footnotes, endnotes, comments, footers, headers, headings etc. etc. * The initial selection on this dialog will depend on how or from where you got into the F dialog. For example, if the comment context menu had an item called "search comments", it would bring up F with only comments checked; but the main menu item would not do that. One can bike-shed what the default selection should be, and whether using the same menu item from different places should affect the default. * The initial selection can be overriden by a parameter of the UNO command, which would be a list of checked/selected items. So, the way a "search comments" would be implemented is the F dialog command, with a setting of the initial selection parameter to only have comments. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148648] Need to make Insert cross-ref more accessible
https://bugs.documentfoundation.org/show_bug.cgi?id=148648 --- Comment #2 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #1) > Shortcuts are precious and hard if not impossible to remove later. Fair enough... > What key combination do you have in mind? Anything would be better than no shortcut, I guess... how about Alt+Shift+R, or Alt+Shift+C? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 139395] Writer Paragraph Style dialog is too tall: OK/Cancel buttons are not visible
https://bugs.documentfoundation.org/show_bug.cgi?id=139395 --- Comment #26 from Mike Kaganski --- Personally I'd prefer the sections made collapsible, remember their collapsed state, and make all dialogs have scrollbars. [/rant off] -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148248] Autofilter menu item label "Text Color" is better to be "Font Color"
https://bugs.documentfoundation.org/show_bug.cgi?id=148248 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com --- Comment #6 from Gabor Kelemen (allotropia) --- Just checked my Excel 2013, they also call it "Filter by Font Color". +1 to change this. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148248] Autofilter menu item label "Text Color" is better to be "Font Color"
https://bugs.documentfoundation.org/show_bug.cgi?id=148248 --- Comment #5 from Joselp --- I don't understand where the problem lies The filter makes it clear if you want to filter by text colour or background colour, but if it is because of inconsistencies in the interface, it would be correct to unify concepts. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148460] IMPROVEMENT ideas for side panels (icons, collapsable)
https://bugs.documentfoundation.org/show_bug.cgi?id=148460 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from Heiko Tietze --- Do you know the View > Navigator F5 panel? You can dock it at the left side and have any other tab at the View > Sidebar Ctrl+F5. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148248] Autofilter menu item label "Text Color" is better to be "Font Color"
https://bugs.documentfoundation.org/show_bug.cgi?id=148248 Heiko Tietze changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||samuel.mehrbrodt@allotropia ||.de See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=76 ||258 --- Comment #4 from Heiko Tietze --- It's a bit unclear in case of View > Value Highlighting. Samuel, was it a deliberate choice? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148648] Need to make Insert cross-ref more accessible
https://bugs.documentfoundation.org/show_bug.cgi?id=148648 Heiko Tietze changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from Heiko Tietze --- Shortcuts are precious and hard if not impossible to remove later. What key combination do you have in mind? It's possible to customize .uno:InsertReferenceField / cross reference. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148673] Should the Bullet and Numbering toolbar also appear with unnumbered (chapter) headings?
https://bugs.documentfoundation.org/show_bug.cgi?id=148673 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #10 from Heiko Tietze --- Let's do it. But making it a duplicate of bug 38850. *** This bug has been marked as a duplicate of bug 38850 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148698] Siebar: Margin settings incorrect for letter size incorrect at the page tab
https://bugs.documentfoundation.org/show_bug.cgi?id=148698 Heiko Tietze changed: What|Removed |Added Summary|Page Format Margin settings |Siebar: Margin settings |incorrect for Letter Size |incorrect for letter size |in LO Writer|incorrect at the page tab Keywords|needsUXEval | Blocks||108650 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Heiko Tietze --- Guess it's a duplicate of bug 135572. *** This bug has been marked as a duplicate of bug 135572 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108650 [Bug 108650] [META] Page deck/tab of the sidebar -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148728] Should Format -> Character/ Paragraph entry's not be called Paragraph/Character Direct Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=148728 Mike Kaganski changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #7 from Mike Kaganski --- (In reply to Telesto from comment #6) > > So when you edit properties of paragraph, you have the dialog named > > "Paragraph". > > You're right if you approach the menu entry from the perspective that the > dialog being about a paragraph, and that's why it called paragraph. > > --- > > I approach differently and do that wrong. It does not "applies Direct Formatting to an Paragraph". It *defined settings* of the paragraph. And there are many properties of a paragraph, many of which are not covered by this dialog. The "direct formatting" is not a correct name for this dialog, no matter how you look at it. Because e.g. character-related properties (DF) of the *paragraph* are not set using this dialog. Only paragraph-related properties of the paragraph. And even then, one direct property is missing - namely, style name itself. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148728] Should Format -> Character/ Paragraph entry's not be called Paragraph/Character Direct Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=148728
Telesto changed:
What|Removed |Added
CC||heiko.tietze@documentfounda
||tion.org
Status|RESOLVED|UNCONFIRMED
Resolution|NOTABUG |---
--- Comment #6 from Telesto ---
(In reply to Mike Kaganski from comment #4)
> * There is an object named "Paragraph". It represents a specific piece of
> text in the document.
Check
> It has own properties, among them: (a) style name; (b)
> everything else.
Check
> Whenever you assign a style to a paragraph, you define that
> paragraph's specific direct property (a); whenever you assign font to a
> paragraph, you assign another direct property (one of (b))...
Check
> So when you edit properties of paragraph, you have the dialog named
> "Paragraph".
You're right if you approach the menu entry from the perspective that the
dialog being about a paragraph, and that's why it called paragraph.
---
I approach differently and have tendency to include what it 'does'. The
paragraph dialog has as object a "specific piece of text in the document". The
dialog applies Direct Formatting to an Paragraph (a specific piece of text in
the document.)
Also observe the following:
1. Open Writer
2. Press Right Click
3. Notice Entry Character & Paragraph
4. Expand one of those
5. To one is for Paragraph' Paragraph.. (DF)
6. Below the separator line there a presets for formatting. In casu these are
Paragraph Styles, but these could have been Paragraph DF presets.
Offtopic comment: I would actually more or less expect Paragraph DF presets
compared to Paragraph DF styles if have paragraph containing 'hello world' and
select only world and right right click you expect to 'style' affect that
specific range but well this is not the case with Paragraph Styles (those are
about the full paragraph). but technically outside the scope here)
7. The last entry is 'Edit Style'.
Offtopic comment: If you right click within a paragraph or select a range of
text followed by right click you expect 'Edit Styles' to affect that specific
range ('this paragraph or this select, I would). However you're actually
editing the style document wide.. (but technically outside the scope here)
--
In my perception paragraph being used used multiple contexts:
1) Paragraph "the specific piece of text in the document".
2) Paragraph as category ((hypernym) contain the settings regarding a Paragraph
Paragraph Style & Paragraph ... (Paragraph DF) (see context menu)
3) Paragraph.. as name for an specific dialog regarding a paragraph. It opens
a Paragraph DF dialog. So you apply Paragraph DF to an Paragraph.
Also if you have a paragraph formatted with a paragraph style, and you open the
Format -> Paragraph dialog some users might (initially) expect LibreOffice to
be 'smart' and get the 'Paragraph Styles' dialog.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148768] New: Test
https://bugs.documentfoundation.org/show_bug.cgi?id=148768 Bug ID: 148768 Summary: Test Product: LibreOffice Version: 7.4.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-b...@lists.freedesktop.org Reporter: heiko.tie...@documentfoundation.org CC: heiko.tie...@documentfoundation.org, libreoffice-ux-advise@lists.freedesktop.org, xiscofa...@libreoffice.org Just testing mail delivery -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148473] Use field type for subtreeing in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=148473 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Heiko Tietze --- Wonder with what categories we end up. Number range, Date/Time, Page Number in case of my formatted dummy text (=> available at the extensions site). But in principle IO agree with more hierarchy for large trees. Could have been also an option for the Foot/Endnote thingy. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148728] Should Format -> Character/ Paragraph entry's not be called Paragraph/Character Direct Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=148728 Heiko Tietze changed: What|Removed |Added CC|heiko.tietze@documentfounda |mikekagan...@hotmail.com |tion.org| --- Comment #3 from Heiko Tietze --- You are right, formatting the paragraph is applied directly on top of the style. But I also agree with Timur, renaming it to Format > Direct Paragraph Format, or the like, confuses the users and wont help to understand the concept. The dialog name is a different question. Also not worth the effort, IMO. Mike, what do you think? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148732] UI: Default Character in Format Styles is called No Character Style in character styles deck of the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=148732 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEW Blocks||108014 Keywords|needsUXEval |difficultyBeginner, ||easyHack, skillDesign, ||topicDesign See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0818 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||sdc.bla...@youmail.dk Ever confirmed|0 |1 --- Comment #1 from Heiko Tietze --- "Default CS" was renamed "No CS" for bug 140818 and this command was obviously missed. The label for .uno:DefaultCharStyle is defined in officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu Seth, one for you? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108014 [Bug 108014] [META] Writer character style bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148272] Cross-reference to numbering wrongly includes separator character
https://bugs.documentfoundation.org/show_bug.cgi?id=148272 --- Comment #9 from Heiko Tietze --- To insert just the number you have to use Numbered Paragraph and Chapter (my example is "Chaper One:" becoming "One"). Nothing has changed to my knowledge with 7.2. Perhaps you share an example documents along with screenshots expected / before 7.2 and unexpected / after 7.2. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148723] Request improvement :Create a REFLECT text effect in Font attributes like italic, bold...
https://bugs.documentfoundation.org/show_bug.cgi?id=148723 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Heiko Tietze --- (In reply to V Stuart Foote from comment #2) > IMHO => WF Concur as those effects are rather fontwork or drawing related to me. But for round trip compatibility with OOXML we need feature parity. => DUP *** This bug has been marked as a duplicate of bug 62185 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148728] Should Format -> Character/ Paragraph entry's not be called Paragraph/Character Direct Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=148728 --- Comment #4 from Mike Kaganski --- (In reply to Heiko Tietze from comment #3) I see that comment 2 is confused/misguided. And nothing needs any change. (In reply to Telesto from comment #2) > If you modify a style a PS style or introduce a new style, the caption of > the dialog will be Paragraph Style: Style name > > The dialog for Paragraph... will be Paragraph. > > A) If it where that obvious, you could call the Paragraph Styles dialog > Paragraph. You are in the styles deck, so it would be a style anyhow. Completely wrong. The two different captions reflect *precisely* what is being edited. * There is an object named "paragraph style", and that is *not* a paragraph, but a named set of properties that *may* be applied to *any* paragraph; so when you edit that *paragraph style* object, it is plain wrong to name the dialog simply "Paragraph": it would mean you edit something different than you in fact are editing. * There is an object named "Paragraph". It represents a specific piece of text in the document. It has own properties, among them: (a) style name; (b) everything else. Whenever you assign a style to a paragraph, you define that paragraph's specific direct property (a); whenever you assign font to a paragraph, you assign another direct property (one of (b))... So when you edit properties of paragraph, you have the dialog named "Paragraph". -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148768] Test
https://bugs.documentfoundation.org/show_bug.cgi?id=148768 Xisco Faulí changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID Component|UI |deletionRequest -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148447] Replace All in Writer comments
https://bugs.documentfoundation.org/show_bug.cgi?id=148447 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | --- Comment #2 from Heiko Tietze --- Don't see a reason why Replace All shouldn't be available. The opposite is true from the UX POV. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148728] Should Format -> Character/ Paragraph entry's not be called Paragraph/Character Direct Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=148728 Timur changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #5 from Timur --- I guess we may close this. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148728] Should Format -> Character/ Paragraph entry's not be called Paragraph/Character Direct Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=148728 Mike Kaganski changed: What|Removed |Added Resolution|WONTFIX |NOTABUG -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148756] Document Type in Options dialog should correspond to the application that opened the dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=148756 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | Ever confirmed|0 |1 Status|UNCONFIRMED |NEW See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||8330 Blocks||112724 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org --- Comment #2 from Heiko Tietze --- Yes, Pete is right. The connected dropdown lists are not intuitive and to initialize it per module is an improvement. Some types are yet not associated with a specific module, namely HTML and Master document. Not a big deal. What bothers me more is what we show when started without module context meaning from the start center. Just the first entry as today, I'd say. And I also struggle with "Text document" thinking of ASCII rather than formatted text. My proposal is to rename the module specific entries with their module name: "Text Documents (Writer)", "Spreadsheets (Calc)"... similar to bug 118330 and bug 118435. It would also be an improvement if the arrangement of the two controls indicate the relationship. Might be a bit too large if we place the two next to each other, though. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112724 [Bug 112724] [META] Options dialog's Load/Save settings bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
