Pavel Sanda schrieb:
what happens for you with this recipe? :
1. newfile, ctrl+m
2. hit two keys \a
3. immediately (before popup appears) hit tab
(before this patch 'acute' gets completed on first hit
and accepted on second hit). now this stops work, so completion
completion
I see your point, but see below:
Now we have no regressions
well, you removed the basic task of completion for a few glitches
in other parts of code.
Sorry but this is the rule: When you add a new feature build it so that it doesn't introduce a
regression except this was a discussed decision.
Navigating in tables and formulas using TAB is there since ever. More important for tables this is
common in all word processors (Word, OOo, etc) and also in programs like Excel and the like. So this
is a basic feature and I don't see why we should remove it for a special case in one new feature.
So what needs to be fixed is completion, not the TAB handling. Could you please inform Stefan Stein
to fix this issue?
So new features need to respect existing behaviors and not the opposite.
while i agree with this sentence, for the time being please put it back.
I don't agree with you here: Now only completion doesn't work when pressing TAB very fast, so this
is not a big problem. More important is that we save 2 regressions.
> the correct solution for tab key will require more time.
Yes, but only on the side of the completion feature.
regards Uwe
