richedit: private movement of cursors in text insertion should not cause WM_NOTIFY to be sent
Alex Villacís Lasso
a_villacis at palosanto.com
Mon Apr 28 12:06:54 CDT 2008
As text is inserted in WM_SETTEXT, the cursor is moved to the end, and
then back to offset 0. A reordering of operations prevents a WM_NOTIFY
from being sent on cursor being moved to the end, and another by being
moved back to the beginning. If the cursor was not at offset 0, then
exactly one WM_NOTIFY must be sent, for the movement from previous
position to the beginning.
With tests to prove this change and the previous one that fixed crash
#1 (modify flag should be off on WM_SETTEXT-caused WM_NOTIFY)
* Private movement of cursors in text insertion should not cause
WM_NOTIFY to be sent.
* Test for above behavior
* Test for modify flag from WM_SETTEXT being unset in the middle of
perl -e '$x=2.4;print sprintf("%.0f + %.0f = %.0f\n",$x,$x,$x+$x);'
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 0 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20080428/0a469103/attachment.bin
More information about the wine-patches