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