https://issues.apache.org/ooo/show_bug.cgi?id=94386

Rainer Bielefeld <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|trivial                     |minor

--- Comment #11 from Rainer Bielefeld 
<[email protected]> ---
(In reply to mroe from comment #9)
> It may be there will be an understanding why the behaviour described in this
> issue is implemented as it is.

That's simple to understand: reason was "Don't know better", "had no time to do
better", "users did not want better" or similar.

(a) Competitors analysis (for Writer Table column width, Calc Column width):
(a1) Kingsoft: ignores unallowed characters like wrong decimal separator,
     alphanumerics, simpy nothing appears in the input line if wrong
     key has been pressed
(a2) SoftMaker FreeOffice: Shows result of key press (unallowed characters
     appear in input field). But with [ok] or <Enter> a message box "Invalid
     Number" appears, [ok] in message box marks input field with invalid number
(a3) AbiWord (I tested indents):
     Unallowed characters accepted in input field , but
     dropped with trailing  input filed contents with <Enter>

Assuming that most wrong inputs might be wrong decimal separator any other
behavior I saw seems smarter than current AOO behavior.

(b) My preferred solution: 
(b1) With <Enter>, [ok] or any other input confirmation ignore
     wrong character and all trailing input field contents
     (Similar to Abi Word).
(b2) As soon as an unallowed input has been done change contents of
     input pane to red (or show red background or red frame or similar
     signal)  to show that current input is invalid.
(b3) If input has become valid again remove signal color. 
     Example: Column width
     "2"      valid
     "2 "     INvalid
     "2 c"    INvalid
     "2 cm"   valid again
     You can see how that works with LibO 4.1 menu 'Tools -> Options
     Language settings -> Languages -> Date recognition pattern string'

The current solution was great for the 1990ties, nowadays users expect some
more.

-- 
You are receiving this mail because:
You are on the CC list for the issue.
You are the assignee for the issue.
You are watching all issue changes.

Reply via email to