Why do you have to lock banks but not pixmaps?

BlitzMax Forums/BlitzMax Programming/Why do you have to lock banks but not pixmaps?

sswift(Posted 2009) [#1]
?


_Skully(Posted 2009) [#2]
Banks carry lots of cash


kfprimm(Posted 2009) [#3]
After checking the source, you don't have to lock it. Locking will simply prevent it from being resized or deleted. Just call BankBuf to get the pointer.


ImaginaryHuman(Posted 2009) [#4]
Allows the bank memory to be moved to a new location by the o/s? I guess. It's a bit like the whole `lockimage` thing. .. you aren't really locking anything, it's just blitz lingo for `i'm planning to modify it now`.


Gabriel(Posted 2009) [#5]
As already stated, you don't have to lock banks. If you're still wondering about locking pixmaps, it's essentially indicating that you want to work on the copy of the image that it's in system memory. You can't modify images in VRam, they have to be modified in system memory and reuploaded, and that's what the whole LockImage to get a pixmap procedure is really about.