[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug in tooltip handling
From: |
Nick Roberts |
Subject: |
Re: Bug in tooltip handling |
Date: |
Tue, 4 Jul 2006 23:42:30 +1200 |
> The only drawback of this is that I load too much (the whole GUD stuff
> instead of only the tooltip functionality), thus consuming a little more
> memory than necessary. Another drawback is that on every mouse event
> `gud-tooltip-tips' is executed (returning nil). If this is all, that's
> no big problem for me.
It returns nil in buffers where GUD tooltips are not meant to work i.e
when the major-mode is not a member of gud-tooltip-modes.
I think thats the problem of just adding to tooltip-hook. You have a list
of functions and the last non-nil one wins.
> Anyway, I think those event-based tooltips are useful for a lot of tasks
> where calculation of the tooltip contents is time-intensive and should
> not be performed beforehand. So splitting it out into an own library
> `event-tooltip' or so would be a good idea.
Well, it's part of the answer.
--
Nick http://www.inet.net.nz/~nickrob
- Re: Bug in tooltip handling, Nick Roberts, 2006/07/02
- Re: Bug in tooltip handling, Leon, 2006/07/02
- Re: Bug in tooltip handling, Tassilo Horn, 2006/07/03
- Re: Bug in tooltip handling, Nick Roberts, 2006/07/03
- Re: Bug in tooltip handling, Tassilo Horn, 2006/07/04
- Re: Bug in tooltip handling,
Nick Roberts <=
- Re: Bug in tooltip handling, Tassilo Horn, 2006/07/04
- Re: Bug in tooltip handling, Nick Roberts, 2006/07/04
- Re: Bug in tooltip handling, Tassilo Horn, 2006/07/05
- Re: Bug in tooltip handling, Nick Roberts, 2006/07/05
- Re: Bug in tooltip handling, Tassilo Horn, 2006/07/05