🚀 go-pugleaf

"Marc" <remove_Bukwheat@axess.com> wrote in message
news:3fb8e5d5$1@newsgroups.borland.com...

> The class subclassing also doesn't seem to work.

You cannot subclass external windows.  If you want to intercept messages
from other applications, then you must use a message hook dll via
SetWindowsHookEx().

> What I am trying to do, is trap the fact that a tooltip is
> about to be displayed, and modify the text of it, and maybe
> even its location if needed.  I already have achieved this
> with system menus, but can't do it with tooltips.  Where does
> widows do its messaging for tooltips?

Tooltips are handled on a per-application, per-window basis.  Each
individual application creates and displays its own tooltip windows when
appropriate, like any other window.

However, even that is not standardized.  VCL apps, for example, handle
tooltips very differently than, say, VB or VC++.  The VCL uses its own
standalone THintWindow class, which has nothing to do with the native
tooltip features provided by the Win32 API.  In fact, the VCL has no concept
of the API tooltips at all.  On the other hand, those applications that do
use true API tooltips will most likely receive a WM_NOTIFY message
containing either a TTN_GETDISPINFO or TTN_NEEDTEXT notification just prior
to displaying the tooltip, so you can try looking for those notifications in
your message hook.


Gambit