The simplest hack I can think of is to simply give your A4 style
bitmaps a data member like in the real A4 bitmaps, and let that be a
buffer to a software bitmap. Also keep a checksum of the data member.
Then at certain critical points see if data's checksum has changed and
apply the changes. A hack, I know...
Kind Regards,
B.
Op 28-08-15 00:15, Jon Rafkind schreef:
Yes that was my hope too. One of the major problems with providing
an A5 implementation for A4 is that directly messing with memory
bitmap data won't work properly. At any time an A4 user could do
bitmap->data[x][y] = ...; or whatever. The closest way to support
this in A5 is to call lock_bitmap() to download the video bitmap
into a memory bitmap and then let the user twiddle whatever they
want, but if there is no obvious API call the user makes before
changing bitmap->data values then there is nothing the API can do
behind the scenes.
There might be a few hacks we can do to try to get around this.
Hopefully not too many projects directly use bitmap data.
On Thu, Aug 27, 2015 at 2:57 PM, Beoran <[email protected]
<mailto:[email protected]>> wrote:
Op 27-08-15 20:53, Jon Rafkind schreef:
BTW the A4-to-A5 repo is
https://github.com/kazzmir/allegro4-to-5
Wow, this is great! Keep up the good work! If this becomes
anywhere near complete I would like for allegro4-to-5 this to
become the official upgrade path for people with large allegro 4
projects.
_______________________________________________
Allegro-developers mailing list
[email protected]
https://mail.gna.org/listinfo/allegro-developers
