IOhannes m zmoelnig wrote:
IOhannes m zmölnig wrote:
of course this needs to be back-checked on osX. now that there are help-patches it should be fairly easy. chris: great object, btw.
ah i forgot: wouldn't it be even greater, if the objects wouldn't be so restrictive with the size of the image?
proposal: add a header to the shm-segment where some basic information (xsize,ysize,colorspace,...) is stored; this way, the [pix_share_read] would only need to know the shm_id (and this could even be made settable at run-time) [pix_share_write] would need to know the maximum size of the image to allocate the memory.
mfg.frew IOhannes