RE: [AD] Potential color conversion bug |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: <alleg-developers@xxxxxxxxxx>
- Subject: RE: [AD] Potential color conversion bug
- From: "Robert Ohannessian" <ROhannessian@xxxxxxxxxx>
- Date: Mon, 20 Jun 2005 10:57:07 -0700
- Thread-index: AcV1wGQAEYpRJa37SNuwl6/nmGeC0wAAP8Kg
- Thread-topic: [AD] Potential color conversion bug
Well, allegro_gl_set_allegro_mode() would certainly help.
> -----Original Message-----
> From: alleg-developers-admin@xxxxxxxxxx [mailto:alleg-
> developers-admin@xxxxxxxxxx] On Behalf Of Elias Pschernig
> Sent: Monday, June 20, 2005 10:49 AM
> To: alleg-developers@xxxxxxxxxx
> Subject: RE: [AD] Potential color conversion bug
>
> On Mon, 2005-06-20 at 10:41 -0700, Robert Ohannessian wrote:
> > > On Mon, 2005-06-20 at 10:14 -0700, Robert Ohannessian wrote:
>
> > Something's fishy here. Can you trace down AGL and see which vtable
> > function ends up being called here, and which path is taken?
> >
> > Thanks.
> >
>
> Yes, just did. In the memory case, it uses
> allegro_gl_screen_blit_from_memory, and then blits using glDrawPixels,
> in the video case, it uses allegro_gl_screen_blit_to_self, and then
> blits using glBegin(GL_QUADS);
>
> Which looks right to me..
>
> But something actually is fishy, because it doesn't blit to (0/0), but
> somewhere in the middle of the screen - and a white rectangle appears
> during the second test. Maybe the example misses
> allegro_set_projection() or something?
>
> --
> 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