[futurebasic] Re: Locking and unlocking Pixels

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : March 1998 : Group Archive : Group : All Groups

From: Charlie Dickman <charlied@...>
Date: Fri, 27 Mar 1998 21:26:46 -0500
>When I use the custom function FN SetCPixel  (Not the toolbox call, but the
>very quick  one that uses an array of pixel row addresses calculated at the
>startup to poke values directly into the PixMap) is it necessary to leave the
>PixMap that I'm using locked? Throughout the entire length of the program?
>Will the row addresses change, and will I get garbage? And will it then crash?

You must lock the pixels before you CopyBits or do anything that might move
memory around before you're done updating but you can unlock them when you
are not accessing them. Yes, the addresses will change and yes, it can
cause a crash if you don't keep them locked down and hang on to an address
assuming that the next time you need to reference it it will be in the same
place.

Charlie Dickman
charlied@...