<div><span class="gmail_quote">On 4/4/06, <b class="gmail_sendername">Stefan Dösinger</b> <<a href="mailto:stefandoesinger@gmx.at">stefandoesinger@gmx.at</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">> > 1) Allow XVidMode to init for gamma control regardless the setting of<br>> > UseXVidMode.<br>
> > I already sent a patch for this.<br>> ><br>> > 2) Make UseXVidMode default to "Y".<br><br>> > Let me know what any of you think is best. I'd prefer the first one so<br>> > that I won't have people scratching their heads over what is going on.
<br>> > Though #2 might be more correct than #1. Something should be changed<br>> > because it's silly that Diablo 2 cannot run by default.<br>><br>> We should probably do both #1 and #2. I don't think there's any reason
<br>> to have it disabled by default.<br>Hm. How does that interact with XRandr? There are still mouse grab issues in<br>some games(half-life comes to mind), often because games do not care to grab<br>the mouse. In this case using XVidMode will cause the mouse to leave the
<br>window, which is really disturbing.<br><br>But if XRandr will still be used for screen resolution setup, than this is<br>fine.<br><br>Stefan</blockquote>
<div> </div>
<div>I haven't had a mouse leave the window in a long time.. Probably because I use DXGrab (unless that has been deprecated)...</div>
<div> </div>
<div>Tom</div><br> </div>