🚀 go-pugleaf

In a previous article, slahiri@magnus.acs.ohio-state.edu (Santanu Lahiri) says:

>I am beginning a port of one application I wrote for DOS.  It requires
>me to run multiple instances of a code fragment within the program.
>Specifically, a list box to select a file.  Now, I have the basic file
>selection window working just fine and dandy.  Unfortunately, the listbox
>approach I took requires declaring static handles for the listboxes within
>the window procedure.  (I create several listboxes on receiving the WM_CREATE
>message)
>
>What happened was that I accidentally clicked on the FILE/OPEN menu item of
>the parent window, and opened a second file selection window.  The new window
>came up, worked fine and exited.  Unfortunately the first window was now dead.
>I could work with the list boxes themselves, but the boxes would no longer
>communicate with eachother.  The reason?  The handles had been whacked by
>the second instance of the window.
>
Use a property entry to store the handles in. Property lists are ideal for 
temporary handle storage. Remember to release them when the window is closed.

PCH
-- 
Peter C. Haller				|	'If you do what you 
Imagination Processing Systems		|	have always done,
aa596@cleveland.Freenet.Edu 		|	expect what you have
"Are we having fun yet?"		|	always recieved.'