1. Window Notification Messages
I have mentioned this before and I am still not satified with
using negative decimal numbers in in place of the constants
in the WM_NOTIFY codes ( NMHDR.code )
A Notification code is an UNSIGNED value.
In the windows COMMCTRL.H header
TTN_FIRST is defined as (0U-520U) -- for tooltips
In the win32lib
TTN_FIRST is defined as -520
I think it should be #FFFFFDF8
Also I think that all of the notification codes in COMMCTRL.H header
that are in this (0U-520U) form should NOT be defined with a minus
value but in their long HEX form.
The reason for this is that if you are peeking at a NOTIFICATION
message and you use peek4u ( the logical assumption when checking
notification messages ) you will never see the CORRECT message
to respond to; you have to use peek4s instead.
I think this can cause errors and confuse someone trying to write
new code for the library
I searched through the window examples and win32lib but no one
seems to be using these notification codes.
PS: Coming soon WIN32ERU.EX
Bernie
Bernie
2. Re: Window Notification Messages
- Posted by euman at bellsouth.net
Aug 08, 2001
I do all of mine the long way, for instance.
4294901760 instead of (-65536),
4294901761 instead of (-65535),
4294901762 instead of (-65534),
you get the picture.
I believe the same as you do about this....
BTW, I use WM_NOTIFY alot!
Euman
euman at bellsouth.net
> I have mentioned this before and I am still not satified with
> using negative decimal numbers in in place of the constants
> in the WM_NOTIFY codes ( NMHDR.code )
>
> A Notification code is an UNSIGNED value.
>
> In the windows COMMCTRL.H header
> TTN_FIRST is defined as (0U-520U) -- for tooltips
>
> In the win32lib
> TTN_FIRST is defined as -520
>
> I think it should be #FFFFFDF8
>
> Also I think that all of the notification codes in COMMCTRL.H header
> that are in this (0U-520U) form should NOT be defined with a minus
> value but in their long HEX form.
>
> The reason for this is that if you are peeking at a NOTIFICATION
> message and you use peek4u ( the logical assumption when checking
> notification messages ) you will never see the CORRECT message
> to respond to; you have to use peek4s instead.
>
> I think this can cause errors and confuse someone trying to write
> new code for the library
>
> I searched through the window examples and win32lib but no one
> seems to be using these notification codes.
>
> PS: Coming soon WIN32ERU.EX
>
> Bernie
> Bernie
>
>
>
>
>
