James Hawkins wrote:
which is why this code is not in WineHQ.
What is it exactly that is keeping this code out of wine? Just curious because if it's something that just needs to be worked on, we should let developers know so we can get started on that.
The current riched32 is wrong. It should not be based on the edit control. While it is, no incremental improvement is possible. The code I sent in the previous mail is not going in to WineHQ any time soon, so that somebody will have motivation to fix Richedit 2.0 properly, which is the path forward for Richedit 1.0 also.
Mike
