Anyway, let us say this strange requirement has its root in performance and implementation issues.
The main problem is that Image is sort of "immutable", which allows it to cache host platform resource handle. That is not possible with ImageBuffer, whose content can change at any moment.
If it would be supposed to work in "non-ugly" way, ImageBuffer <-> Image conversions would require the full copy of ImageBuffer pixels.
In practice, you should use ImageBuffer only as local variable, "Image content accesor". Or be very very careful...
Members
Pages
Help
Register
Login
Home
