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

List:       ktexteditor-devel
Subject:    Re: texthint interface (kde4)
From:       Hamish Rodda <rodda () kde ! org>
Date:       2005-07-28 14:23:23
Message-ID: 200507290023.25338.rodda () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi,

On Thu, 28 Jul 2005 03:55 am, Joseph Wenninger wrote:
> There is the old texthint interface, which I never implemented for kate
> though and, since it was very limited from the the begining on (I know,
> I've created the interface, but I'm not proud of it)

I tried to implement this for Kate about a year ago.  I found problems 
relating to when the hint should be hidden:

* when one text hint has been completed, should the timer really start again?
if the user missed the spot, and they move the cursor again, they have to
wait the elapsed time again.  QTooltips for widgets work on a delay-once,
show as many until interrupted (mouse click, move/focus off widget, key press
etc).

* probably the biggest problem is that the interface doesn't enable the client
to specify what text range (ie. start and end cursors) the tooltip
applies to, thus how far the mouse has to go before the tooltip is invalid.
This is especially important if we decide the above behaviour should not mean
re-starting the timer.  It's of course easy to add.

* what happens when multiple hints are offered by various components (or even 
one component).

Also I think we should make it easy to have nicely styled / presented hints.

Cheers,
Hamish.

[Attachment #5 (application/pgp-signature)]

_______________________________________________
Ktexteditor-devel mailing list
Ktexteditor-devel@kde.org
https://mail.kde.org/mailman/listinfo/ktexteditor-devel


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