On 1/19/07, Jacob Alberty jacob.alberty@vetmanage.com wrote:
I am a delphi developer (not limited to this language, I have done several projects in C, C#, as well as assembly but for the purposes of this email I am a delphi developer). I am experiencing some weirdness in regards to the richedit control in regards to database access (Specifically TDBRichEdit), Since I am a delphi developer using wine this means I have access to A) My programs source code, B) Delphis VCL source code (So i can view how delphi manages the richedit control which in this case is split up among 3 files) and C) The Wine source code. I have two questions 1) Since Delphi does not actually implement any of richedits features, merely wraps around them I should be in the clear to create a patch to wine to correct this functionality correct? and 2) What method is best to watch the api interaction going on in my application so I can see if wine is returning any weirdness that it shouldnt (do normal windows api spy programs work under wine?).
Jacob, If you have any specific issues with wine's richedit control, you can always file a bug on bugs.winehq.org (and be sure to mark it as in the wine-richedit component). I haven't personally tried any api spy programs, so I can't vouch for them - but I've usually had success with just using the environmental variable WINEDEBUG ("WINEDEBUG=+richedit wine application.exe"). If you have any questions about how the richedit component works, feel free to ask me directly. When making changes, we encourage writing tests (see the dlls/riched20/tetsts folder) to demonstrate that the new behavior is, in fact, the correct behavior. Also, when you make a change make sure to run the tests already there to make sure you haven't caused any existing tests to fail. Thanks, --Matt