[Bug 160072] Inconsistent handling of objects on Calc sheets with select all (Delete, clear contents, copy-paste)
https://bugs.documentfoundation.org/show_bug.cgi?id=160072 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |NOTABUG See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9800 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |RESOLVED Keywords||needsUXEval Summary|Inconsistent handling of|Inconsistent handling of |objects on Calc sheets |objects on Calc sheets with ||select all (Delete, clear ||contents, copy-paste) --- Comment #1 from Stéphane Guillou (stragu) --- Thanks for splitting this from bug 159800, jollytall. My first reaction was: Ctrl + A -> Delete is different to Ctrl + A -> Ctrl + X. This feels inconsistent (also with the Writer behaviour), but I some users' workflows might rely on a way to modify all cells without affecting objects... However, as you noticed, we've got two ways to remove things in Calc (whereas Writer does not seem to make the distinction): - Delete: directly removes cell contents - Backspace (same as "Clear Contents" in context menu): offers a dialog. The default removes text, date & time, comments, numbers, formulas - which matches what Delete does. But one can pick and choose what gets deleted, and can delete absolutely everything with one tick of a box. Options are remembered, so it's then easy to Backspace + Enter. (In reply to jollytall from comment #0) > It has a strange side-effect, that if a sheet is Ctrl-A, Ctrl-C and another > sheet is also Ctrl-A, Ctrl-V then the objects on the target sheet remain > there. It think this has to be the case, as the objects are two separate elements, with different names assigned to them, as can be seen in the navigator. One can't expect LO to replace an object just because it is of same type and is anchored to the same cell. And a single cell can have as many objects anchored to it as we desire. Paste Special gives a large number of options to decide exactly what is pasted. It's different for cell contents, as it is straight-forward to understand the model of pasting cell contents over others at the same coordinates. So leaning towards "resolved - not a bug", but set back to "unconfirmed" if you still think something needs changing. Copying the UX/Design team in just in case. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160011] Hidden columns should not prevent text from preceding columns from overflowing over their cells
https://bugs.documentfoundation.org/show_bug.cgi?id=160011 --- Comment #11 from m_a_riosv --- I think the main issue about changing the behavior is the modification of the display for existing documents, without any warning to the user. IMO, the possible performance problems are surely solvable, because it seems that the cases where you need to modify the display are limited to show hide column(s). Perhaps it could be a concern, if the cells of the hidden columns were massively modified by macro. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 116342] EDITING: Clicking inside text box does nothing
https://bugs.documentfoundation.org/show_bug.cgi?id=116342 Gabor Kelemen (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0071 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 148184] FORMATTING create a means to represent an integer as an IP Address
https://bugs.documentfoundation.org/show_bug.cgi?id=148184 Buovjaga changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org Whiteboard| QA:needsComment| -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159652] Finding a way to join a suffix to the word immediately before it, using autocorrect function
https://bugs.documentfoundation.org/show_bug.cgi?id=159652 Heiko Tietze changed: What|Removed |Added Component|Writer |Documentation Status|NEEDINFO|REOPENED Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||olivier.hallot@libreoffice. ||org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159652] Finding a way to join a suffix to the word immediately before it, using autocorrect function
https://bugs.documentfoundation.org/show_bug.cgi?id=159652 --- Comment #12 from Mac --- (In reply to Heiko Tietze from comment #11) > (In reply to Mac from comment #8) > > ...with prefixes whatever is after the prefix doesn't get corrected... > > (In reply to Shantanu from comment #9) > > This (use of comma) workaround is intended for those who already know the > > correct spelling > > ... I find frustrating is that it's not adequately documented... > > Since the ticket is still flagged as UX relevant I wonder what's missing. Or > should we forward the solution to documentation? Oh, by all means, my initial question/request has been answered beautifully. It's a neat method for such highly inflective language as Polish (and, I gather, Marathi). So, it can go to documentation as a solution for adding suffixes and inflective morphemes that need to be automatically attached to the root word (while also get autocorrected - as a bonus - if there's need for that) --- Since you are asking what is missing - it's the autocorrection of the root word in the middle (the part without the the .* pattern and non-space separator). In other words: prefix[corrected],root[not corrected],suffix[corrected] (the root may stay not autocorrected because the autocorrect function recognises it not as the root alone, but as the chain consisting of [prefix][comma][uncorrected root]. Although I'll have to investigate it once again, because Im almost positive the root got corrected in a few words I initially typed as a test. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159486] Infobars' close (X) buttons' invisible hitboxes too small and hard to click
https://bugs.documentfoundation.org/show_bug.cgi?id=159486 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Assignee|libreoffice-b...@lists.free |heiko.tietze@documentfounda |desktop.org |tion.org Keywords|needsUXEval | Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #3 from Heiko Tietze --- White-space is your friend... -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159652] Finding a way to join a suffix to the word immediately before it, using autocorrect function
https://bugs.documentfoundation.org/show_bug.cgi?id=159652 Heiko Tietze changed: What|Removed |Added Status|REOPENED|NEEDINFO --- Comment #11 from Heiko Tietze --- (In reply to Mac from comment #8) > ...with prefixes whatever is after the prefix doesn't get corrected... (In reply to Shantanu from comment #9) > This (use of comma) workaround is intended for those who already know the > correct spelling > ... I find frustrating is that it's not adequately documented... Since the ticket is still flagged as UX relevant I wonder what's missing. Or should we forward the solution to documentation? -- You are receiving this mail because: You are on the CC list for the bug.
