Re: [Mesa3d-users] Losing control of demo apps...

[Chris W. <re...@se...>]

Another data point...I've found that the demo apps retain control of the
input when I run them as root, but lose control of input events when I ru
them as a non-priveleged user. Haven't tried this with Quake yet, but
that's the case with all of the apps in Mesa-3.2/demos and
Mesa-3.2/3Dfx/demos/.

Is there a env variable or compiler option I'm missing?

-Chris

On Thu, Jun 08, 2000 at 02:31:45PM -0600, Brian Paul wrote:
> Chris Woodfield wrote:
> > 
> > I have a Voodoo3 AGP card, and I've compiled Mesa 3.2 with the latest
> > version of glide (downloaded from wdfx last week).
> > 
> > So far, every Mesa application I've attempted to run (from the demos to
> > Quake II) has refused to take keyboard or mouse control. In every case,
> > I've had to remotely kill the app, and even then I don't always get my
> > console back.
> > 
> > 1. In situations like this, how does one get the 3dfx driver to give X
> > back the screen?
> > 
> > 2. How to you force the Mesa app to take keyboard and mouse control?
> 
> 
> Remember, when you open a full-screen 3dfx display, you're not really
> creating an X window.  So, whatever X window happens to have focus
> "underneath" the 3dfx display will get the input events.
> 
> Check out the Mesa-3.2/demos/glutfx.c for one way to deal with
> this.
> 
> I haven't run QuakeII in a long time.  Don't know what the problem
> is there.
> 
> -Brian
> 
> _______________________________________________
> Mesa3d-users mailing list
> Mes...@li...
> http://lists.sourceforge.net/mailman/listinfo/mesa3d-users

-- 
---------------------------
Christopher A. Woodfield		re...@se...

PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B