fixme:richedit:RICHED32_WindowProc Unknown message 129
Good day! Thanks, Daniel Walker, for your work on riched32. I don't know what or why is richedit and I'm kind of GUI-challenged, or I'd have a go at implementing these myself, but I have an app that uses it, so if traces would help, just say which traces and if you want them for builtin or native riched32. The app fails with a bogus message box: "Insufficient memory or disk space" after these three fixme's with the builtin, so those traces should be pretty short, but maybe it would also be useful to try to use spy on the native riched32. If spying on msvcrt, mfc42, and/or the app's own dll's is likely to make noise, I can filter it out, but at this point I don't know. fixme:richedit:RICHED32_WindowProc Unknown message 129 fixme:richedit:RICHED32_WindowProc Unknown message 528 fixme:richedit:RICHED32_WindowProc Unknown message 130 Regards, Lawson
lawson_whitney(a)juno.com wrote:
Good day!
Thanks, Daniel Walker, for your work on riched32.
Your welcome ..
I don't know what or why is richedit and I'm kind of GUI-challenged, or I'd have a go at implementing these myself, but I have an app that uses it, so if traces would help, just say which traces and if you want them for builtin or native riched32. The app fails with a bogus message box: "Insufficient memory or disk space" after these three fixme's with the builtin, so those traces should be pretty short, but maybe it would also be useful to try to use spy on the native riched32. If spying on msvcrt, mfc42, and/or the app's own dll's is likely to make noise, I can filter it out, but at this point I don't know.
fixme:richedit:RICHED32_WindowProc Unknown message 129 fixme:richedit:RICHED32_WindowProc Unknown message 528 fixme:richedit:RICHED32_WindowProc Unknown message 130
This patch will take out the fixme msgs , but I don't think it will fix anything.. You will have to run your application with "--debugmsg +edit,+richedit" to should show you any errors/msgs from the controls. Let me know what happens .. Daniel Walker Index: richedit.c =================================================================== RCS file: /home/wine/wine/dlls/richedit/richedit.c,v retrieving revision 1.15 diff -u -r1.15 richedit.c --- richedit.c 2002/01/14 19:44:07 1.15 +++ richedit.c 2002/01/15 13:56:49 @@ -98,6 +98,14 @@ switch (uMsg) { + case WM_NCCREATE : + DPRINTF_EDIT_MSG32("WM_NCCREATE"); + return 1; /* Return TRUE to continue creation. */ + + case WM_NCDESTROY: + DPRINTF_EDIT_MSG32("WM_NCDESTROY"); + return 0; + case WM_CREATE : DPRINTF_EDIT_MSG32("WM_CREATE"); @@ -507,6 +515,9 @@ return SendMessageA( hwndEdit, uMsg, wParam, lParam); /* Messages known , but ignored. */ + case WM_PARENTNOTIFY: + DPRINTF_EDIT_MSG32("WM_PARENTNOTIFY"); + return DefWindowProcA( hwnd,uMsg,wParam,lParam); case WM_NCPAINT: DPRINTF_EDIT_MSG32("WM_NCPAINT"); return DefWindowProcA( hwnd,uMsg,wParam,lParam);
On Tue, 15 Jan 2002, Daniel Walker wrote:
fixme:richedit:RICHED32_WindowProc Unknown message 129 fixme:richedit:RICHED32_WindowProc Unknown message 528 fixme:richedit:RICHED32_WindowProc Unknown message 130
This patch will take out the fixme msgs , but I don't think it will fix anything.. You will have to run your application with "--debugmsg +edit,+richedit" to should show you any errors/msgs from the controls. Let me know what happens ..
Daniel Walker
I didn't mean to complain about a few fixme's. Removing them doesn't help, of course, and I don't see anything that looks like an error in this. My guess is that the app expects the parent to do something on being notified. Hmmm, I can not get a +snoop=riched32 trace with the native riched32. That frustrated me the last time I beat my head against this app and riched32. +snoop simply hangs, and +edit,-snoop=msvcrt produces a huge trace, but the only mention of riched is in some strings to mfc42.6442. Well, maybe you can make some sense of it, and if not, where's the harm? Lawson
On Tue, 15 Jan 2002 lawson_whitney(a)juno.com wrote: [...]
Hmmm, I can not get a +snoop=riched32 trace with the native riched32. That frustrated me the last time I beat my head against this app and riched32. +snoop simply hangs, and +edit,-snoop=msvcrt produces a huge trace, but the only mention of riched is in some strings to mfc42.6442.
What happens when snoop hangs? Does the process seem to get into an infinite loop? I once had a problem with +snoop where it would get into an infinite loop when the pointer was 0xffffffff (-1). I did not have time to get to the bottom of this at the time and now I am not sure I can even reproduce the problem. But I did work around the problem by checking for -1 before doing the string check. See the attached patch. +snoop was looping where I added the TRACEs. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The software said it requires Win95 or better, so I installed Linux.
On Tue, 15 Jan 2002, Francois Gouget wrote:
What happens when snoop hangs? Does the process seem to get into an infinite loop?
No, it just stops. (well, I guess it could be looping in something not being traced, except that the cpu is idle).
I once had a problem with +snoop where it would get into an infinite loop when the pointer was 0xffffffff (-1). I did not have time to get to the bottom of this at the time and now I am not sure I can even reproduce the problem.
But I did work around the problem by checking for -1 before doing the string check. See the attached patch. +snoop was looping where I added the TRACEs.
-- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The software said it requires Win95 or better, so I installed Linux.
________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/web/.
participants (3)
-
Daniel Walker -
Francois Gouget -
lawson_whitney＠juno.com