Thanks jfk.
I'm not too worried about speed. I expect any method to be fairly slow.
That's the problem right there. If I use, for example, a 600x600 image (or I guess even 513x513), it will be scaled up to 1024*1024 automatically. After scaling it back down again the data is quite badly degraded. I really need the original data for each pixel.
I can load an alpha channel from a separate 8 bit png and apply it (using your own routine from the code arcs). This works fine but I can't really expect end users to create a separate image for the alpha. Too messy.
If only loadtexture could be forced to tile or 'pad' a wrong-sized image instead of scaling it I would be sorted, but I don't think that's possible.
EDIT - Is it my imagination, or does the 'preview' button now actually post what you've written?
- resizing an image is pretty slow.
I'm not too worried about speed. I expect any method to be fairly slow.
- no pixelperfect alpha channel due to resize
That's the problem right there. If I use, for example, a 600x600 image (or I guess even 513x513), it will be scaled up to 1024*1024 automatically. After scaling it back down again the data is quite badly degraded. I really need the original data for each pixel.
I can load an alpha channel from a separate 8 bit png and apply it (using your own routine from the code arcs). This works fine but I can't really expect end users to create a separate image for the alpha. Too messy.
If only loadtexture could be forced to tile or 'pad' a wrong-sized image instead of scaling it I would be sorted, but I don't think that's possible.
EDIT - Is it my imagination, or does the 'preview' button now actually post what you've written?