🚀 go-pugleaf

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

> My question is "What return value???"  this is a notification
> message, there is no return value.

Yes, there is:

    WM_NOTIFY
    ...
    Return Values
        The return value is ignored except for notification messages that
specify otherwise.

TTN_SHOW specifies otherwise, because it needs to know whether the tooltip
has to be positioned automatically or if the application is controlling
that.  If you use Spy++ or other similar tool, you will see that WM_NOTIFY
is sent via SendMessage(), not PostMessage().  Messages sent with
SendMessage() always have a return value , even if just the default of 0.
So yes, WM_NOTIFY (and TTN_SHOW in particular) expects a return value, just
as the documentation says.

> How do I use this message correctly to be able to move my window.

A WH_CALLWNDPROC hook is not allowed to alter messages, let alone be able to
return values for them.  The only thing your hook procedure can return is
the result of the hook itself, not the message it processes.
WH_CALLWNDPROCRET, on the other hand, has access to the return value of the
message, however WH_CALLWNDPROCRET hooks aren't allows to modify the message
data, either.

> I have managed to hack a solution but I have a small glitch.
> On the WM_WINDOWPOSCHANGING message I verify
> if its a tooltip and if its not at postion 0,0 and the call a
> SetWindowPos with the new location.  This displays the TT in
> the new location properly but it first flashes it where it initially
> was suppose to be.  Yes this works but the flash is annoying.

There are several other messages that you can try using instead of
WM_WINDOWPOSCHANGING, such as WM_CREATE, WM_NCCALCSIZE, WM_GETMINMAXINFO,
WM_SHOWWINDOW, etc.


Gambit