[1/2] richedit: Moved optional message loop in tests to its of function.
dylan.ah.smith at gmail.com
Fri Oct 10 15:37:13 CDT 2008
The message loop was put in for debugging according to the comment, and
is only shown when an environment variable is set. The only reason I
see for having the message loop outside of the tests is for finding
missing DestroyWindow calls at the end of the tests, since all the tests
end with destroying the windows to clean up.
I have found this message loop helpful for debugging tests by inserting it
within one of the tests to pause it and see what is going on. I decided
that this took too much effort, so I created this patch that moves the
existing message loop to a function so that I can simply add in a call to it
when I needed to for testing.
dlls/riched20/tests/editor.c | 37 ++++++++++++++++++++++---------------
1 files changed, 22 insertions(+), 15 deletions(-)
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
More information about the wine-patches