On 15 Sep 2002 06:59:46 GMT, ? staggered into the Black Sun and said:
>> Looks like X assumes there is one and only one active pointer at any
>> time. There are references in the X documentation to a "core
>> pointer", which makes me think there must be a "non-core pointer",
>> but I couldn't find anything coherent about what the differences are
>> or how to use them.
>> Also, I don't think you've thought the UI through on this. How do
>> you tell which pointer is associated with which mouse? (Move
>> pointer, grab the wrong mouse, curse, drop wrong mouse, pick up right
>> mouse. Repeat 50 times per hour.) Maybe it'd work for you, though.
> Hi, I've got an idea justifying using 2 mice in an X session.
> Play a well designed two-person game on a big screen with your
> close partner. The game will assign different cursor shapes to
> the 2 mice so the players won't get confused. Using two separate
> computers/screens to play networking games tends to alienate
> people, while playing games on the same screen will contribute
> to a better relation, I suppose.
I dunno, I've played many a good game of Starcraft or C&C or Marathon
with people on the LAN and I don't think anybody felt alienated.
(fragged, Engineer-0wned, or Reaver-dropped, maybe...)
Quote:> If this idea is silly, please let me know.
Not silly at all--it'd just be a lot of work to do if X doesn't support
having more than 1 mouse pointer! I'm trying to figure out if it does
or not, but there's an awful lot of code to wade through and the
documentation doesn't even mention this.
I suppose you could test your idea out with less work on the X backend
using a joystick and a mouse... player 1 has the mouse, player 2 has the
joystick, both control a different onscreen sprite that does something.
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /
http://www.brainbench.com / "He is a rhythmic movement of the
-----------------------------/ penguins, is Tux." --MegaHAL