rogerson@PEDEV.Columbia.NCR.COM (Dale Rogerson) (07/12/90)
The WINDOWS.H file and the Reference manual that I just got with the Windows SDK 3.0 do not have the following messages defined: WM_DROPOBJECT 0x022A WM_QUERYDROPOBJECT WM_BEGINDRAG WM_DRAGLOOP WM_DRAGSELECT WM_DRAGMOVE 0x022F There message numbers are not used in the new header file and a space is left for them. Anyone know what happened to them? For those interested these are the messages sent between the File Manager and the Program Manager when you move a file to the Program Manager. Run Spy to see this. -----Dale Rogerson-----
dianek@umd5.umd.edu (Diane Kurilecz) (07/13/90)
In article <3144@PEDEV.Columbia.NCR.COM>, rogerson@PEDEV.Columbia.NCR.COM (Dale Rogerson) writes: # # The WINDOWS.H file and the Reference manual that I just got with # the Windows SDK 3.0 do not have the following messages defined: # WM_DROPOBJECT 0x022A # WM_QUERYDROPOBJECT # WM_BEGINDRAG # WM_DRAGLOOP # WM_DRAGSELECT # WM_DRAGMOVE 0x022F # # There message numbers are not used in the new header file and a # space is left for them. Anyone know what happened to them? There are several text files you should read which are included with the sdk. This question is explained in windev\tips.txt. The follow- ing is quoted without permission: - --------------------------- - 1.3 Drag and Drop Messages - --------------------------- - - The Drag and Drop messages that Program Manager and File - Manager use are for internal use of these programs and are - not currently documented. The DRAG and DROP protocol for - manipulating program icons within groups is being - redesigned. Once the design effort is complete, - documentation will be issued to explain how to use these - messages in a compliant manner. Until then, however, - Microsoft is not able to support the use of those messages. - This, however, does not stop you from implementing your own - series of messages. - - The only message of this type that we are currently - documenting is WM_QUERYDRAGICON. **diane m kurilecz