Hi,
are there any future plans to write more straight-to-texture-ram objects like pix_imageInPlace?
an equivalent to pix_image (singular) or a buffer that doesn't need sequentially named files would be nice
i may be misinformed but i don't see any reason to use pix_image processes for static images - as they seem to consume more resources
and another question - is there currently a way to convert a raw list of numbers into an image, as a pix_set object does, but store it in a buffer along with other images? i think this might be a flexible option with an object like pix_imageInPlace
J
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2013-12-12 04:35, j-p wrote:
Hi,
are there any future plans to write more straight-to-texture-ram objects like pix_imageInPlace?
no not currently. i do have plans however for a replacement for [pix_imageInPlace] and [pix_multiimage] using [pix_buffer]. probably an object that uploads an entire [pix_buffer] to textures.
and another question - is there currently a way to convert a raw list of numbers into an image, as a pix_set object does, but store it in a buffer along with other images?
[pix_set]+[pix_buffer]?
gasdmr IOhannes
-
IOhannes m zmoelnig -
j-p