MDI windows, MDIClient and mdiclient
Boaz Harrosh
boaz at hishome.net
Mon Oct 20 04:21:22 CDT 2003
I always use OutputDebugString (Win32 API), or TRACE macros under msvc
headers.
Than it shows under the Debugger. And if on-site, Just download for free
the DebugMon application from:
www.sysinternals.com <http://www.sysinternals.com>
It will catch and display all your Traces and let you save them to
file and more..
Free Life
Boaz
Shachar Shemesh wrote:
> Dmitry Timoshkov wrote:
>
>> "Shachar Shemesh" <wine-devel at shemesh.biz> wrote:
>>
>>
>>
>>> I am trying to make an application work under wine. The app is
>>> probably an MFC app, that defenitely uses MDI. The problem boils
>>> down to this - it tries to create an MDI window by doing
>>> SendMessageA to a message of type "WM_MDICREATE". Here's the catch -
>>> the class it wants to use is in Unicode. This fails for obvious
>>> reasons.
>>>
>>
>>
>> And what are that obvious reasons? AFAICS we do proper ansi/unicode
>> conversions for WM_MDICREATE message in windows/winproc.c.
>>
>>
>>
> When you send things via the "SendMessageA", I would assume they need
> to be ANSI. As such, the "obvious reasons" are that it appears, to my
> understanding of things, that this SHOULD fail.
>
> I'm trying to write a regression test, to see whether it doesn't fail
> on Windows. If anyone has any idea how to create traces on Windows
> that are similar to --debugmsg +relay, please let me know (I remeber
> that someone said something about it in the past).
>
> Shachar
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-devel/attachments/20031020/ab0fa5bf/attachment.html
More information about the wine-devel
mailing list