While testing an application which I have (mostly) running under Wine, I consistently see the following message sent sometines to RICHEDIT32_WindowProc and sometimes to TOOLTIPS_WindowProc:
msg: 0xc01e wp: 0 lp: 0x40596d60
Any clues as to what this message is would be welcome.
-- Chuck Crayne ----------------------------------------------------------- ccrayne@crayne.org -----------------------------------------------------------
i have tried everything. how does one unsubscribe?
unsubscribe-wine-devel@winehq.com does not work.
----- Original Message ----- From: ccrayne@crayne.org To: wine-devel@winehq.com Sent: Sunday, April 14, 2002 1:39 PM Subject: Unknown Windows message number
While testing an application which I have (mostly) running under Wine, I consistently see the following message sent sometines to RICHEDIT32_WindowProc and sometimes to TOOLTIPS_WindowProc:
msg: 0xc01e wp: 0 lp: 0x40596d60
Any clues as to what this message is would be welcome.
-- Chuck Crayne
ccrayne@crayne.org
"GoneWest" == GoneWest gonewest@ptdprolog.net writes:
GoneWest> i have tried everything. how does one unsubscribe? GoneWest> unsubscribe-wine-devel@winehq.com does not work.
GoneWest> ----- Original Message ----- From: ccrayne@crayne.org To: <totally unrelated message cited in TOFU style deleted>
No, you didn't try the obvious. Either look at the instructions you receieved when you where granted the subscription you requested or by searching www.winehq.com.
Bye
"ccrayne" == ccrayne ccrayne@crayne.org writes:
ccrayne> While testing an application which I have (mostly) running ccrayne> under Wine, I consistently see the following message sent ccrayne> sometines to RICHEDIT32_WindowProc and sometimes to ccrayne> TOOLTIPS_WindowProc:
ccrayne> msg: 0xc01e wp: 0 lp: 0x40596d60
ccrayne> Any clues as to what this message is would be welcome.
Please look if you find c01e as the result of some call before. I suspect the application to register some message with RegisterWindowMessage and 0xc01e should be the result. The messages starting from 0xc000 are reserved for RegisterWindowMessage. But I don't have an idea what to do with that message...
Bye