Corrected winproc fix
daveh-wine at cadlink.com
Thu Feb 28 14:34:48 CST 2002
OK, I the simple fix I posted earlier for the winproc memory leak problem
caused two identical winprocs to be stored and broke some of the common
controls (causing a message loop). This fix should keep the winproc ordering
correct and only allow one winproc of the same address if it is set as a
both a class and user proc.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 773 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20020228/0755d13a/winproc.obj
More information about the wine-devel