RE: [AD] Potential color conversion bug

["Robert Ohannessian" <ROhannessian@xxxxxxxxxx>]

Ahh, much better. I wonder what state causes the problem.

Either way, it would still be nice to get the Allegro change, but it
isn't necessary. I can work around it in AllegroGL if needed by
duplicating Allegro's blit() code inside the vtable for
blit_between_formats().


> -----Original Message-----
> From: alleg-developers-admin@xxxxxxxxxx [mailto:alleg-
> developers-admin@xxxxxxxxxx] On Behalf Of Elias Pschernig
> Sent: Monday, June 20, 2005 11:16 AM
> To: alleg-developers@xxxxxxxxxx
> Subject: RE: [AD] Potential color conversion bug
> 
> On Mon, 2005-06-20 at 10:57 -0700, Robert Ohannessian wrote:
> > Well, allegro_gl_set_allegro_mode() would certainly help.
> >
> 
> Yes, now it works as expected, and also the times changed:
> 
> 32 -> 32
> mem 4.290000
> 32 -> 32
> vid 1.680000
> 
> Peter, can you also try adding allegro_gl_set_allegro_mode() after
> set_gfx_mode()?
> 
> The docs here:
> http://allegrogl.sourceforge.net/docs/group__allegro.html#ga1
> say:
> "
> You should encapsulate all Allegro code dealing with the screen in
> between allegro_gl_set_allegro_mode() and
> allegro_gl_unset_allegro_mode()
> "
> 
> So I assume, the od dbehavior in the original example was expected,
and
> there is no bug at all?
> 
> --
> Elias Pschernig
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers