RE: [AD] Mouse events getting through to other consoles |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: <alleg-developers@xxxxxxxxxx>
- Subject: RE: [AD] Mouse events getting through to other consoles
- From: "Vincent Penecherc'h" <Vincent.Penecherch@xxxxxxxxxx>
- Date: Wed, 23 Nov 2005 14:35:40 -0000
- Thread-index: AcXwOm1iWMbw/xb5Rkm0wDl29SvMZwAAB9Gg
- Thread-topic: [AD] Mouse events getting through to other consoles
> Not to me, but I'm curious: does this bug also show up if you
> don't use
> modules and staticlink?
Good question.
About modules, however, I don't think mouse drivers can
be built as modules, can they ?
I'll try static linking. I think I see what you're hinting
at - only one copy of Allegro reads stuff, but data gets
duplicated per user program ?
Also, Annie doesn't see that problem, she's still using
4.2.0-rc2, Linux 2.4.13 (I'm using 2.4.16), and using the
SIGALRM version (I'm now using the pthread version, with
joy (I can profile, and gdb works!)), which made me say
I suspected the threading bit.
Anyway, I'll do the static thing soon and post the results.
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________