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

List:       kdevelop-devel
Subject:    Re: Completion list suggestion
From:       Erlend Hamberg <ehamberg () gmail ! com>
Date:       2009-05-06 23:37:01
Message-ID: 200905070137.07208.ehamberg () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 7. May 2009 00.33.47 David Nolden wrote:
> In general I do like the idea. The only problem is that exactly this same
> mechanism is already now used to switch from simple "automatic" completion
> mode into full "user-invoked" completion mode within kdevelop.
>
> This means that when there is a simple completion, and the user presses
> CTRL+Space, he sees more.

Ah, ok. Didn't know it worked like that.

> Now one could of course implement that when he presses _again_, the next
> item in the list is selected. That should be pretty easy to implement
> within katecompletionwidget.cpp and kateviewinternal.cpp.
>
> It should then probably be like this: When the current completion is not
> yet an user-invoked completion, do the same thing we do now.
> When it already is a user-invoked completion, move to the next item instead
> of starting it again.

That sounds like a good idea.

Needless to say, I would be really happy if this was done. :)

-- 
Erlend Hamberg
"Everything will be ok in the end. If its not ok, its not the end."
GPG fingerprint: 45C3 E2E7 86CA ADB7 8DAD 51E7 3A1A F085 AD3B CF19 

["signature.asc" (application/pgp-signature)]

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel


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