[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 100203] Autocomplete - Make it easier to skip it
From:       Maciej Pilichowski <bluedzins () wp ! pl>
Date:       2006-04-25 17:22:51
Message-ID: 20060425172251.22866.qmail () ktown ! kde ! org
[Download RAW message or body]

------- 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=100203         




------- Additional Comments From bluedzins wp pl  2006-04-25 19:22 -------
Autocompletion works great when intended but it is really hard to quit when it is not \
intended.

Example, I have "const" and "const_iter" on the list, I write method which is \
constant

void Foo::foo() const[enter]

guess what happens.

There should be specific settings for autocompletion:
keys:
[ next item ]
[ previous item ]
[ confirmation ]
[ quit ] -- the key is "killed"

any other key (non-character, not edit-key, like del) should quit (transparently! the \
key should not be killed) autocompletion. Plus settings for handling cycling /you are \
at the top of the list and press [prev item]/ o   cycle
o   don't cycle 
o   quit popup

The last option cycling+quit is really useful -- this way I could write my text or \
code with transparent help from autocompletion.

It would be great /extreme wish :-)/ if modifier-keys "tapping" could be used. For \
example shift * 2 for confirmation.


[prev in list] [next in list] [prev in thread] [next in thread]