[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2006-02-21, Elias Pschernig <elias@xxxxxxxxxx> wrote:
> On Wed, 2006-02-22 at 00:51 +1100, Peter Wang wrote:
> > > Well. I think, all the vtable entries could have a target parameter,
> > > like this:
> > >
> > > al_line(x, y, z) {
> > > active_display->vtable->line(active_display, x, y, z);
> > > }
> >
> > Ok, but now you need to make sure the first `active_display' reference
> > is not different from the second `active_display' reference.
>
> If it is a thread-local variable, it can't possibly be different.
Yes, you're right.
> > > > Though it honestly doesn't matter too much anymore, as I assume OpenGL
> > > > will be the graphics API of choice for future Allegro programs.
> > >
> > > I doubt that. If I use Allegro, then the reason is most likely that I do
> > > not want to deal with all the complexity of something like OpenGL. And
> > > if I need 3D transforms, shading, and everything else, then I probably
> > > wouldn't use Allegro at all.
> >
> > You'd still need input and sound and timing, not to mention that opening
> > an OpenGL window is quite a lot of work in of itself, and is not
> > cross-platform.
> >
>
> Yes. But still, Allegro's gfx API should be much more high level than
> OpenGL.
Anyway, what I was saying originally was, if the majority want there to
be a thread-specific, current target, and there are no major technical
problems, then I won't mind too much.
Peter