Help wanted: Implementing Wine dlls that need access to X11 commands.
farmboy1 at subdimension.com
Wed Jan 15 16:23:38 CST 2003
On Wednesday 15 January 2003 19:09, Robert North wrote:
> Robert North 7ownq0k402-at-sneakemail.com |Wine Mailing Lists| wrote:
> >>> Now, as it turns out, the methods to interrogate a wintab
> >>> message queue are extremely similar to those to interrogate an X11
> >>> message queue.
> >>> So that's +1 to giving wintab it's own X11 message
> >>> queue. (Or possibly even one X11 msg queue per tablet context!).
> >>> A simple X11<->wintab mapping can be implemented, and no
> >>> additional queue data structs are needed in the wintab
> >>> implementation.
> >> I'm not convinced you can avoid managing an event queue for wintab
> >> events; from a quick look at the spec I doubt you can simply map the
> >> wintab functions to X11 queue functions.
> > I'm about to have a final look at this, see if there is a clear mapping
> > from X11 functions to wintab.
> > More on this once I've completed my investigations.
> > One mismatch is that wintab uses a fixed size message queue which can be
> > defined as, as opposed to Wine or X11.
> > (I'm assuming wine or X11 are either extremely large queues, or
> > dynamically sized.).
> I've re-checked the X11 code, and you're right, the only sane way to map
> X11 events to a wintab queue is by coding an event queue for wintab.
Sorry if this seems like a stupid question.
Could you please elaborate what the problems between X11, DirectDraw, OpenGL
and accessing X11 functionality are.
I am not an expert in either area but like to understand the problem.
More information about the wine-devel