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

List:       ktexteditor-devel
Subject:    Re: texthint interface (kde4)
From:       Vladimir Prus <ghost () cs ! msu ! su>
Date:       2005-09-01 13:07:58
Message-ID: 200509011707.58427.ghost () cs ! msu ! su
[Download RAW message or body]


Harald Fernengel 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)
> >
> > What do users of such an interface really need ? eg for displaying values
> > of variables in kdevelop. Which functions, slots or signals would a user
> > really need ?
> >
> > I would appreciate if this mail starts a brainstorming thread on
> > ktexteditor-devel
> 
> In an ideal world, I would get a signal with the row and column of the 
> pointer. Then, I could do my processing and send another signal with the 
> results. If the mouse pointer hasn't moved in between, the hint would be 
> shown.
> 
> This way we could do more complex things like asking the debugger 
> asynchronously for symbol values and display them when the debugger
> responds.  
> If I'd do it synchronously, the ui would freeze until I could retrieve the 
> values.

Yes, that would be very good. Right now I'm trying to implement variable 
tooltips in KDevelop using old tooltip interface, and the only solution I see
is:

1. When needTextHint is invoked, issue gdb request
2. Setup eventFilter that would handle all mouse events
3. When gdb replies, check if the mouse has moved, if not, show tool tip.

Which is not overly nice approach.

- Volodya


_______________________________________________
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]