https://bugs.documentfoundation.org/show_bug.cgi?id=149145
--- Comment #10 from ady <[email protected]> --- (In reply to studog from comment #8) > (In reply to Buovjaga from comment #3) > > For me, the autoinput is working per column and it doesn't pick up strings > > from other columns. I don't see any of the behaviour you describe. > You'll notice that the problematic text prediction in my original report is > by column. A1 contains a sample string. A2 is where the prediction occurs. That only means that all your prior mentions of "exact steps" (with or without additional symbols) are incorrect, as your "step 4" in comment 0 points to the wrong cell address, which explains why other users cannot replicate the behavior. As for the behavior you described, I am guessing that redrawing every pixel of every cell and every layer for every individual inserted character (or any kind of edition), and also for every AutoInput reaction, and for every Spell-check reaction, would result in an unbearable low performance (or unreasonable request for additional resources). After [ENTER], a screen refresh is effectively and successfully done, as expected. Moreover, similar issues are seen when editing a (long) formula within a cell, which makes it not-so-easy to click on adjacent cells (for instance, to use such adjacent cell as argument of a function). Whichever the content of a cell, it has to take priority over other layers on screen, until the edition of the cell is finalized. The behavior also depends on cell's alignment. IMNSHO, this is a very minor issue. -- You are receiving this mail because: You are the assignee for the bug.
