https://bugs.documentfoundation.org/show_bug.cgi?id=149145
--- Comment #12 from studog <[email protected]> --- (In reply to ady from comment #10) > 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. _arg_ You are correct. This is a case of me reading what I expected I had written instead of what I actually wrote. Thanks for the spot. It doesn't look like I can edit that comment to fix it though. > 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). I disagree. This should be pretty quick: on drawing the prediction, save the underlying graphics state; on cancelling the prediction, restore the state. > After [ENTER], a screen refresh is effectively and successfully done, as > expected. Correct. There is a workaround. > Whichever the content of a cell, it has to take priority over other layers > on screen, until the edition of the cell is finalized. This is the point though. The predicted text is not content, and once cancelled does not exist. What it was covering should be redrawn. > IMNSHO, this is a very minor issue. I agree the priority is low, given the workaround. -- You are receiving this mail because: You are the assignee for the bug.
