ok. in that case its really needed. .width / .height don't work as they should, they don't have the real image width/height saved of the image that is held in VRAM ... thats plain crap but ok.
Remember, Max2D is trying to act like a 2D system, so it stands to reason that the texture resizing should be hidden from the user. It would be nice if the real texture size was stored somewhere though (Unless it is and I've missed it?). or if the internal handling changed since BM 1.06 for which this function was written
It's always been that way. Is it ok, if I add that to my code?
Of course you can.[edit]
Apologies to hub for the thread hi-jack...
[/edit]