[Libreoffice-ux-advise] [Bug 98362] Behavior interpreting input: 1-, 1+ are treated as number, not as text

2020-09-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98362 Heiko Tietze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Libreoffice-ux-advise] [Bug 98362] Behavior interpreting input: 1-, 1+ are treated as number, not as text

2020-09-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98362 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #15

[Libreoffice-ux-advise] [Bug 98362] Behavior interpreting input: 1-, 1+ are treated as number, not as text

2020-09-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98362 --- Comment #14 from Thomas Lendo --- I assume the program should make the work for users as efficient as possible. If somebody types a non-number-only input into a cell, then Calc should not change the input but the cell format to text

[Libreoffice-ux-advise] [Bug 98362] Behavior interpreting input: 1-, 1+ are treated as number, not as text

2020-09-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98362 --- Comment #13 from Heiko Tietze --- You can force 1- with cell format as text. But this would still be interpreted as a number. Since I don't see any good use case for 1- being pure text I vote for WF. -- You are receiving this mail

[Libreoffice-ux-advise] [Bug 98362] Behavior interpreting input: 1-, 1+ are treated as number, not as text

2020-08-31 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98362 Thomas Lendo changed: What|Removed |Added Keywords||needsUXEval CC|