Dmitry Timoshkov wrote:
Shachar Shemesh [EMAIL PROTECTED] wrote:
In case anyone is interested - http://shemesh.biz/winetrace.bz2
Again unicows.dll (Microsoft Layer for Unicode) plays bad games
with Wine. Could you regenerate the log with additional +snoop?
Same location. What is
Shachar Shemesh wrote:
Dmitry Timoshkov wrote:
Shachar Shemesh [EMAIL PROTECTED] wrote:
In case anyone is interested - http://shemesh.biz/winetrace.bz2
Again unicows.dll (Microsoft Layer for Unicode) plays bad games
with Wine. Could you regenerate the log with additional +snoop?
Same
Shachar Shemesh [EMAIL PROTECTED] wrote:
While talking about it, what is unicows.dll? I've tried to find
anything about it in the list archives.
It's the Microsoft Layer for Unicode allowing to run under win9x
some unmodified applications which use unicode win32 APIs.
Will trying to get
Dmitry Timoshkov wrote:
Shachar Shemesh [EMAIL PROTECTED] 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
Hi
I hope I'm not stating the obvious here, I'm just trying to help.
I'm trying to find my way around the MDI setting, and phrase a regression test.
However, I cannot seem to create the exact same circumstances. When looking at the
original app using Spy++, I see that the application has a
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
It will catch and display all your Traces and let you save them to
file and more..
Boaz Harrosh wrote:
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
Doesn't help me much when I have sources for neither program nor APIs.
I'm trying to see why a propritery program misbehaves under wine, by comparing it to
Windows. When running it under Windows, I don't have the luxury of OutputDebugString.
What about Spy++ for messages? For system calls
I'm trying to see why a propritery program misbehaves under wine, by comparing it to
Windows. When running it under Windows, I don't have the luxury of OutputDebugString.
Maybe even better:
http://www.codeproject.com/useritems/DLL_Injection_tutorial.asp
Already with a sample about logging
Shachar Shemesh [EMAIL PROTECTED] wrote:
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.
No, it shouldn't. The conversion should take place in the case of
Dmitry Timoshkov wrote:
Shachar Shemesh [EMAIL PROTECTED] wrote:
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.
No, it shouldn't. The conversion
Dmitry Timoshkov wrote:
Shachar Shemesh [EMAIL PROTECTED] wrote:
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.
No, it shouldn't. The conversion
Shachar Shemesh [EMAIL PROTECTED] wrote:
In case anyone is interested - http://shemesh.biz/winetrace.bz2
Again unicows.dll (Microsoft Layer for Unicode) plays bad games
with Wine. Could you regenerate the log with additional +snoop?
--
Dmitry.
Hi all,
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
Shachar Shemesh wrote:
Hi all,
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
I am using MSDN July 2001.
Just look up WM_MDICREATE at the bottom of the page you have links to an
over-view and all important functions/messages.
Basically you:
- Create any frame window but call MdiFrameProc for default processing.
- Create a child MDIClient as you have seen. sub-class it or
Shachar Shemesh [EMAIL PROTECTED] 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
17 matches
Mail list logo
