G_Lock
Posted: Jun 2, 2004 @ 3:53pmDoes setpixel use a different function internally after a call to G_Lock?
The reason I ask is because of my experience with pocketfrog and it's lock function.
With PF, you get a pointer to the buffer so you can do direct access, so what's the point of a G_Lock that doesn't return a pointer?
It also seems like doing a lock on a surface just to plot one pixel (as in simple3.ppl) is a bad thing to do (if it works like the lock in pocketfrog).
The reason is that on devices with a non-native NORTH display orentation, all 320x240 pixels must be rotated before and after the lock. It only makes sense if you are going to be doing a LOT of pixel operations.
The reason I ask is because of my experience with pocketfrog and it's lock function.
With PF, you get a pointer to the buffer so you can do direct access, so what's the point of a G_Lock that doesn't return a pointer?
It also seems like doing a lock on a surface just to plot one pixel (as in simple3.ppl) is a bad thing to do (if it works like the lock in pocketfrog).
The reason is that on devices with a non-native NORTH display orentation, all 320x240 pixels must be rotated before and after the lock. It only makes sense if you are going to be doing a LOT of pixel operations.