Aug. 23, 2012
12:41 p.m.
On 23.08.2012 13:00, Camillo Bruni wrote: > On 2012-08-22, at 20:22, Henrik Sperre Johansen <henrik.s.johansen@veloxit.no> wrote: > >> Is it just me who finds the new text completion resulting from O/E merge insufferably disruptive? >> Whenever I've been editing in an existing method, and try moving back/forward using arrow keys, instead of moving the cursor, it opens a browser on the completion suggestion for whatever I'd just finished writing (if I go right), or does jack squat (if I try moving left)... >> Ironically, clicking the text editor anywhere BUT the completion dialogue leaves the window open, and starts suggesting for whatever you type at the cursors new location, while clicking ON any part of the popup-pane CLOSES it. >> moving cursor with the mouse (not that you could before), only thing that works is pressing escape, which is a natural key to reach for whenever you've finished typing a word, no? >> Not to mention, if there is only one suggestion, and that suggestion you've already typed in completely, it DOES NOT CLOSE. >> >> Suggestions: >> - Don't hijack the arrow keys (at least not left/right) for autocomplete-popup functionality. >> - Close the fracking dialogue if the only suggestion it has is _exactly what is already typed_ >> - Handle mouse-clicks on a suggestion by selecting it, clicks anywhere else in the texteditor by closing it. > maybe I have some time at ESUG to fix this. The solution is to add options for these behaviors, > so everybody is happy You mean someone might LIKE - keep getting suggested something they just typed? - that the window doesn't close when they've clearly change context by moving the cursor? - that the window doesn't respond to mouse input to it by selecting what you clicked on, but rather closing? Cheers, Henry