[Libreoffice-ux-advise] [Bug 140900] [Feature Request] A setting to change the size of the font previews dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=140900 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 140900] [Feature Request] A setting to change the size of the font previews dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=140900 --- 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.
[Libreoffice-ux-advise] [Bug 141456] Separate outline browsing and heading browsing in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=141456 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #12 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #10) > What's really bothering me is seeing non-headings in the tree for headings. > > ... > > I have a document with heading styles applied, but also with paragraph style > which have an outline level. They're not section headings. I don't want to > see them in Headings view in navigator. They have an outline level because I > want them to participate in numbering. The participation of outline levels in numbering means what exactly? I *guess* you mean things like table captions or formula numbering (created using respective numbering fields); and the intended use of that feature is exactly per-chapter numbering - thus the outline level being a synonym of chapter is clear, again. But indeed, one is not forced to use features only as intended - any creative (mis)use is OK. But when one would use outline levels for that, one could limit the outline levels in Navigator to only those levels that are used for chapters. Again: using features outside of their intended use (outline level of paragraphs = (sub)chapter heading) is OK, but not a reason to introduce some changes that make everyone's life (except yours) much harder. Most (MOST) users would be confused (to put it politely) if your proposal is implemented. > I understand that you're stating, or claiming, that Outline level = Heading > level. But as long as different names are used, then they're not. These > words are not synonyms. They are. The "words" in any program are not "words of human language". They are terms, and they mean specific things in the program, and that meaning should not (and cannot) match all the breadth of meaning the human language word bears. The LibreOffice Writer's Outline level is the same as LibreOffice Writer's Heading level. Period. > Outlines = Headings = Chapters > > any of those two false equivalencies is annoying, but how can you seriously > defend both of them, while keeping the triple-inconsistent names? So - your problem in this discussion is just that you believe that you know how we should use words, and if we are allowed or not to use some of them as synonyms. And you know what, you may discuss that (renaming the three to a single term), and it might even make sense - but it is not what this issue is about. Closing WONTFIX again (in fact, it should be INVALID, because WONTFIX means "there's a problem, but resolving it is undesirable", while this is "I do not want to believe that the term means what it really means"). Nothing to discuss here. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141456] Separate outline browsing and heading browsing in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=141456 --- Comment #11 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #10) > (In reply to Mike Kaganski from comment #7) > > and for now, LibreOffice only > > uses outline level of paragraphs to e.g. create ToC. > > Also for numbering. But I'll grant you it's not that much. What's really > bothering me is seeing non-headings in the tree for headings. No one claimed that outline level is only used for ToC, and for nothing else. If you tried to read what I wrote, you could see that "e.g.", which implies "for this, but not only for this", in addition to the contraposition (implied in the whole description, but also explicit in the next sentence discussing that LO does not use heading styles specially). Again: the sentence you incorrectly quotes meant not "outline level is used exclusively for ToC, and for nothing else", but "to build ToC, only outline level is used by default by LO, and nothing else is used to build ToC by default". Sorry for having to clarify this. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141456] Separate outline browsing and heading browsing in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=141456 Eyal Rozenberg changed: What|Removed |Added Resolution|WONTFIX |--- Status|RESOLVED|UNCONFIRMED --- Comment #10 from Eyal Rozenberg --- Heiko, we're in the middle of a conversation, so please don't just close this as WONTFIX. Anyway... (In reply to Mike Kaganski from comment #7) > and for now, LibreOffice only > uses outline level of paragraphs to e.g. create ToC. Also for numbering. But I'll grant you it's not that much. What's really bothering me is seeing non-headings in the tree for headings. > what is > the intended *use case* for what you propose; what *real-life problem* > should if solve. I have a document with heading styles applied, but also with paragraph style which have an outline level. They're not section headings. I don't want to see them in Headings view in navigator. They have an outline level because I want them to participate in numbering. I understand that you're stating, or claiming, that Outline level = Heading level. But as long as different names are used, then they're not. These words are not synonyms. You mentioned an official LO definition - can you link to it? I must say this reminds me of another inconsistent annoyance, which is that in LO, Outlines = Chapters, but the project refuses to name things consistently (bug 141452). Oh yes, I see you mentioned this too. So, with this additional artificial synonym, we now have: Outlines = Headings = Chapters any of those two false equivalencies is annoying, but how can you seriously defend both of them, while keeping the triple-inconsistent names? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 140900] [Feature Request] A setting to change the size of the font previews dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=140900 --- Comment #7 from chameleonsca...@protonmail.com --- $ xdpyinfo | grep -B 2 resolution screen #0: dimensions:3840x2160 pixels (1016x571 millimeters) resolution:96x96 dots per inch -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 140900] [Feature Request] A setting to change the size of the font previews dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=140900 --- Comment #6 from chameleonsca...@protonmail.com --- I will also provide mine when I get back to it but seeing your screenshot I can already say it looks small to me. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 140900] [Feature Request] A setting to change the size of the font previews dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=140900 --- Comment #5 from chameleonsca...@protonmail.com --- If you're happy with how things are I think it would be interesting to know what your screen's size and resolution are because this request is heavily dependent on it. Just to be clear I don't experience any unintended behavior with this list. It's just a subjective feature request. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141016] Dropdown list disabled in Form if no primary key defined in data model
https://bugs.documentfoundation.org/show_bug.cgi?id=141016 --- Comment #6 from Alex Thurgood --- My suggestion to Frank would be to file a new bug report, or seek out an existing report, and add comments to that existing report, about an enhancement request to support editing of data in mysql table through the LO user interface without the requirement for primary key. The requirement for a primary key in order to be able to add/modify data in a table or linked tables is an artificial, and somewhat arbitrary, limitation imposed by the LibreOffice Database code. I don't believe that there is any easy fix to this either, but if it was someday implemented correctly, it would solve the problem exposed here by the OP. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148394] We need search capability restricted to the Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=148394 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Heiko Tietze --- *** This bug has been marked as a duplicate of bug 43511 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148381] closing the print preview page - with the X, too :)
https://bugs.documentfoundation.org/show_bug.cgi?id=148381 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org --- Comment #4 from Heiko Tietze --- (In reply to sdc.blanco from comment #3) > ... might be friendly to have Calc appear the same as Writer. No objection. Writer uses in sw/uiconfig/swriter/toolbar/previewobjectbar.xml And Calc in sc/uiconfig/scalc/toolbar/previewbar.xml so adding the style might do the trick. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141456] Separate outline browsing and heading browsing in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=141456 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #9 from Heiko Tietze --- (In reply to Mike Kaganski from comment #7) > what is the intended *use case* for what you propose; what *real-life problem* > should if solve. For now, what you suggest only tries to solve some > (possible) terminological confusion, and tries to do that in such a way to > introduce much greater confusion. +1 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148381] closing the print preview page - with the X, too :)
https://bugs.documentfoundation.org/show_bug.cgi?id=148381 --- Comment #3 from sdc.bla...@youmail.dk --- Note that Print Preview in Calc only shows "X", while Writer shows "X Close Preview" -- might be friendly to have Calc appear the same as Writer. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 139433] Form control that renders and displays the html code
https://bugs.documentfoundation.org/show_bug.cgi?id=139433 Heiko Tietze changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #2 from Heiko Tietze --- By using the image form control you can enter the link in the properties dialog. But LibreOffice is not a HTML editor/viewer and adding those capabilities affects security. There are plenty of other methods to "render image in frame" respectively to have it as background. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148407] Need ability to cancel an ongoing paste action
https://bugs.documentfoundation.org/show_bug.cgi?id=148407 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8408 --- Comment #1 from Telesto --- Closely related to bug 148408 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148407] Need ability to cancel an ongoing paste action
https://bugs.documentfoundation.org/show_bug.cgi?id=148407 Telesto changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141389] FORMATTING: Remember and/or indicate the active sheet when managing conditional formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=141389 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Heiko Tietze --- Duplicate of bug 139649? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 131461] Connexion to NextCloud and collaborative editing
https://bugs.documentfoundation.org/show_bug.cgi?id=131461 Heiko Tietze changed: What|Removed |Added Blocks||98360 Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Heiko Tietze --- You can open/save documents remotely per CMIS (File > Save Remote...). The dialog allows to configure a wide range of connections including WebDav to Nextcloud. And of course you may open files on NC with LibreOffice Online. Please reopen in case I missed the point. https://help.libreoffice.org/latest/en-US/text/shared/guide/cmis-remote-files-setup.html https://help.libreoffice.org/latest/en-US/text/shared/guide/digitalsign_receive.html Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98360 [Bug 98360] [META] CMIS bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 123727] PIVOTTABLE Allow use of text columns as Data Fields
https://bugs.documentfoundation.org/show_bug.cgi?id=123727 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #4 from Heiko Tietze --- I'm still having trouble to follow the use case. Using something like One =rand() One =rand() One =rand() Two =rand() Two =rand() Two =rand() etc. works nicely with colA as category in the pivot table. And I cannot wrap my mind around text as data field: What is the sum of colA? The request on ask.libreoffice looks rather as if you try to merge two datasets. There are other methods. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 141479] Enable sheet protection when sharing a spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=141479 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Heiko Tietze --- How do you know if the document is being shared? Do you save remotely? Please describe your workflow a bit more detailed. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 JO3EMC changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |4003| --- Comment #9 from JO3EMC --- I'm sorry. In Bug 144003, the automatic recognition of language groups does not seem to be wrong. It seemed that the handling of punctuation marks was just strange. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148381] closing the print preview page - with the X, too :)
https://bugs.documentfoundation.org/show_bug.cgi?id=148381 Heiko Tietze changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #2 from Heiko Tietze --- (In reply to V Stuart Foote from comment #1) > ...the 'Print Preview' is just a Toolbar, not an app frame > ... > Just don't see much need for the work it would require-- or the current > button suffice. IMHO => WF Fully agree. No inconsistency here. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 148257] Missing/unexposed ability to explicitly set the "language group" of a piece of text
https://bugs.documentfoundation.org/show_bug.cgi?id=148257 JO3EMC changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4003 --- Comment #8 from JO3EMC --- After that, I noticed ... The Bug 144003 issue in Japanese may be related to this issue. In vertical writing (RTL), Japanese characters are automatically recognized in the wrong language group when Western characters are followed by punctuation marks. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 140267] Improve primary key creation when creating/importing a table
https://bugs.documentfoundation.org/show_bug.cgi?id=140267 Heiko Tietze changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.
