| Re: [AD] Windows Addition for Message Parsing |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Wed, 2008-10-08 at 09:40 -0400, Evert Glebbeek wrote:
> On 7 Oct 2008, at 23:48, Trent Gamblin wrote:
> > I like the idea of this and want to apply it to 4.3 and 4.9
> > (probably under a different name). I would change the name of the
> > function though... perhaps win_set_wndproc_callback? Any suggestions
> > or objections?
>
> Personally, I think we should get rid of as many platform dependent
> functions, extensions and hooks as we can (part of me isn't happy
> with ALLEGRO_OPENGL and ALLEGRO_DIRECT3D for that reason). So I'd
Same. I'd be for removing ALLEGRO_DIRECT3D. The idea of ALLEGRO_OPENGL
is to indicate that a display created with it also should provide an
OpenGL context for its window. This is completely platform neutral, and
in theory orthogonal to whether Allegro itself uses OpenGL for its own
drawing or not. The flag only says "This program will use the OpenGL API
to do rendering." - which, as far as I understand, always was one of the
base goals for A5 so we wouldn't have to clone the entire OpenGL API
ourselves. (ALLEGRO_DIRECT3D just is driver selection, which I think
should be done somewhere else.)
> like to see if there's a platform-neutral API that can be used
> (tricky, if we're going to pass messages from the OS back to the
> user) before implementing something like this. Also, couldn't this be
> implemented somehow on top of Allegro's event system (a user
> registers a function that can filter events before they are passed
> into the queue)?
> Other than that I don't have any real objections.
>
As he needs the actual *Windows* messages - it always will be platform
dependent. If we add something similar for OSX and X11, the user will
have to deal with completely different messages, so guess it might as
well be completely separate functions.
The ideal solution would be for us to add support for multiple mice so
there would not even be the need to intercept platform messages. Not
sure what the consequences for the API would be. Likely we'd need some
kind of general device enumeration, instead of the classic
one-mouse/one-keyboard/one-joystick idea (not sure about the latter, it
seems more advanced already). Likely not really worth the effort.
--
Elias Pschernig <elias@xxxxxxxxxx>