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. Dave Hawkes
Attachment:
winproc.diff
Description: Binary data
