On 7/27/12, Jens Alfke wrote:
> Keep in mind that accessing the image pixels directly can hurt drawing
> performance. Your code can only access the pixmap if it's in system RAM,
> while GPU acceleration requires that the pixmap be in VRAM. So messing with
> the pixels may either cause the pixmap t
Keep in mind that accessing the image pixels directly can hurt drawing
performance. Your code can only access the pixmap if it's in system RAM, while
GPU acceleration requires that the pixmap be in VRAM. So messing with the
pixels may either cause the pixmap to be copied back and forth, or force
On Jul 27, 2012, at 7:45 AM, Graham Cox wrote:
> On 27/07/2012, at 10:36 PM, Vojtěch Meluzín wrote:
>
>> I need to create and manipulate an image, which I could access directly
>> from memory and at the same time be able to use system drawing functions
>> for optimization. On Windows I can create
On 27/07/2012, at 10:36 PM, Vojtěch Meluzín wrote:
> I need to create and manipulate an image, which I could access directly
> from memory and at the same time be able to use system drawing functions
> for optimization. On Windows I can create a memory bitmap, but it seems it
> is on possible on
Hi,
I need to create and manipulate an image, which I could access directly
from memory and at the same time be able to use system drawing functions
for optimization. On Windows I can create a memory bitmap, but it seems it
is on possible on Mac, or is it? Note that I don't want to do any
conversi