2008/6/27 Dylan Smith dylan.ah.smith@gmail.com:
Currently msftedit.dll is implemented by loading riched20.dll and then riched20.dll registers the classes that msftedit.dll normally register. Native msftedit.dll appears to be a full implementation of the richedit controls, rather than a wrapper.
Here are the options that I can think of:
- We could continue to implement msftedit.dll as a wrapper around
riched20.dll. This patch would be a step in that direction.
Of course this looks most sane. But I'm asking if you're going to make use of the dwEmulatedVersion other than "< 0x200"? That is, under what circumstances we should emulate version 2 or 3 when we have support for version 5? It's interesting to me, because it seemed to me that the native versions (starting with 2.0) are very compatible to each other.
-- Ph.