[Bug 55276] autocompletion part has strange behavior

[Jens Dagerbo]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=55276     




------- Additional Comments From jens.dagerbo at swipnet.se  2003-11-14 05:37 -------
bleh. hit the wrong button.. :)

I agree that KDevelop doesn't do this gracefully, but I still think the main part of the problem lies with Kate, as:

1. KDevelop doesn't immediately trigger the autocompletion box after an undo, it's only after the regular timeout it happens, and so it is quite possible to undo past a triggerpoint - you only need to be quick enough :)

2. It's very hard, if not impossible, for KDevelop to know that the textChanged() signal it receives is a result of an undo operation.

3. The "multiple undo" case isn't the only to hit upon this issue. It's quite possible to mistype and receive an autocomplete box as a result and then, again, you can't undo your way out of it (using ctrl+z or whatever the shortcut happens to be, it is possible with the toolbar button).

So, IMHO and without knowing anything about the Kate code in question, if katepart simply closes the autocompletion box when the user hits the undo shortcut, the major part of this problem is solved.