And I don't think it makes much sense to implement only single value, because it'd also be a dirty hack =)

Now that I think about it, while we didn't have time to implement the full-blown priority management, we indeed should've at least tried to make a simple scheme allowing to enable/disable acceleration for a particular image.

I don't see implementing the special case of 0.0f as a dirty hack I see it as fulfilling the specification of the method!

Quote

priority - a value between 0 and 1, inclusive, where higher values indicate more importance for acceleration. A value of 0 means that this Image should never be accelerated. Other values are used simply to determine acceleration priority relative to other Images.

So, specifying a value of 0 should prevent the image from being accelerated - and at the moment it doesn't :p

yup, I havn't managed to crash it when changing resolution/bitdepth/refreshrate/fullscreen etc etc.

I have noticed that 8bit fullscreen is veeeeeery slow though, almost as slow as a software back buffer.I'm guessing blits to an 8bit vram back buffer arn't accelerated (probably because it was super buggy, and they couldn't easily fix it ^_^).

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org