[futurebasic] Re: Clipboard/Memory??

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : December 1997 : Group Archive : Group : All Groups

From: David Blache <tech@...>
Date: Tue, 9 Dec 97 18:05:39 -0600
Pierre A. Zippi wrote:

>add the following line just before PICTURE ON
>IF picHandle&>0 THEN DEF DISPOSEH(picHandle&)
>This will get rid of the previous picture and memory just before 
>creating the new one.  The benefit here is the previous picture will be 
>hanging around at "pichandle&" if you should need it for other purposes.

No.  This is incorrect.  Pictures are a special case.  You should always 
use either KillPicture or ReleaseResource*** when disposing of a picture 

***Use ReleaseResource ONLY if the picture was obtained via GetPicture or 
GetResource, and ONLY if the picture is marked as non-purgeable in your 
resource fork.

If the picture is marked as purgeable, then don't do anything - the 
Memory Manager will dispose of it when the time comes.

If the picture was created "on the fly" using the Picture On / Picture 
Off calls, then you should use the KillPicture toolbox call, or even 
better, just set the handle's state to purgeable with the HSetState call 
and be on your merry way.

 (This message was constructed without the use of any Microsoft products)

|    David Blache - STAZologist   /   STAZ Software Technical Support    |
|    STAZ Software * 4387 Leisure Time Drive * Diamondhead, MS  39525    |
|   Orders             800-348-2623   Email:    sales@...   |
|   Technical Support  601-255-7085   Technical: tech@...   |
|   FAX                601-255-7086   WWW: http://www.stazsoftware.com   |
| Join the FutureBASIC programming community now! Send any email to:     |
| futurebasic-subscribe@....                                   |