On 4/15/06, H. Verbeet <[EMAIL PROTECTED]> wrote:
> On 14/04/06, Molle Bestefich <[EMAIL PROTECTED]> wrote:
> > How odd that one flag isn't enough.
> >
> > eg.
> > SwitchResolutionWith = XRandR / XVidMode
> >
> XVidMode is also used for gamma control.
>
>
>
Yes, but I made two patches. One to enab
On 14/04/06, Molle Bestefich <[EMAIL PROTECTED]> wrote:
> How odd that one flag isn't enough.
>
> eg.
> SwitchResolutionWith = XRandR / XVidMode
>
XVidMode is also used for gamma control.
Neil Skrypuch wrote:
> You can tell Wine to use xvidmode instead of xrandr. Add UseXVidMode as Y
> and UseXRandR as N in \HKEY_CURRENT_USER\Software\Wine\X11 Driver.
Aha, that's why my XVidMode=Y didn't work.
How odd that one flag isn't enough.
eg.
SwitchResolutionWith = XRandR / XVidMode
Thank
On Friday, April 14, 2006 05:34, you wrote:
> Neil Skrypuch wrote:
> > Molle Bestefich wrote:
> > > I can switch to 640x480 just fine using [CTRL] [ALT] [-],
> >
> > That uses xvidmode to switch resolutions (and really just changes the
> > amount you can view, the desktop size stays the same, try m
Neil Skrypuch wrote:
> Molle Bestefich wrote:
> > I can switch to 640x480 just fine using [CTRL] [ALT] [-],
>
> That uses xvidmode to switch resolutions (and really just changes the amount
> you can view, the desktop size stays the same, try moving the mouse to the
> edges of the screen). xrandr is
On Thursday, April 13, 2006 09:50, Molle Bestefich wrote:
> Jesse Allen wrote:
> > Molle Bestefich wrote:
> > > Looks like xrandr [support] is broken.
> > > It says "Changing Resolution to 640x480",
> > > so that sounds great - only it doesn't.
> >
> > I'd maybe look through xorg.conf or you X.org
Jesse Allen wrote:
> Molle Bestefich wrote:
> > Looks like xrandr [support] is broken.
> > It says "Changing Resolution to 640x480",
> > so that sounds great - only it doesn't.
>
> I'd maybe look through xorg.conf or you X.org
> log and see what is going on with those refresh frequencies.
Dumb que
Jesse Allen wrote:
On 4/7/06, Molle Bestefich <[EMAIL PROTECTED]> wrote:
trace:xrandr:X11DRV_XRandR_SetCurrentMode Changing Resolution to
1280x1024 @45961 Hz
Starcraft #
Looks like xrandr is broken.
It says "Changing Resolution to 640x480", so tha
On 4/7/06, Molle Bestefich <[EMAIL PROTECTED]> wrote:
> trace:xrandr:X11DRV_XRandR_SetCurrentMode Changing Resolution to
> 1280x1024 @45961 Hz
> Starcraft #
>
>
> Looks like xrandr is broken.
> It says "Changing Resolution to 640x480", so that sounds great - only
>
Jesse Allen wrote:
> > These lines could explain why Starcraft is unable to switch to fullscreen:
> >
> > err:xrandr:X11DRV_XRandR_GetCurrentMode In unknown mode, returning default
> > fixme:xrandr:X11DRV_XRandR_SetCurrentMode Cannot change screen BPP from 16
> > to 8
> > fixme:xrandr:X11DRV_XRand
>On Thu, Apr 06, 2006 at 10:18:16AM +0200, Stefan Dösinger wrote:
>> Because windows' ddraw.dll restores everything when the app exists. I've
>> added
>> some code to do that do my ddraw lib. I restore the screen mode when the
>> ddraw object is released, and on the last DllMain() unload call,
Lionel Ulmer wrote:
Well it's the same for memory: who in his right mind in modern operating
system still 'free's at exit all 'malloc'ed memory :-) ?
Somebody who thinks his code may be reused in a library one day?
Mike
On Thu, Apr 06, 2006 at 10:18:16AM +0200, Stefan Dösinger wrote:
> Because windows' ddraw.dll restores everything when the app exists. I've
> added
> some code to do that do my ddraw lib. I restore the screen mode when the
> ddraw object is released, and on the last DllMain() unload call, I loop
Hi,
> Haha well where that idea comes from is like when Diablo 2 gets the
> gamma error, it has already resized the resolution, but decides to
> quit and not resize it back. Not very nice, but games do funny things
> like that.
Because windows' ddraw.dll restores everything when the app exists. I'
On 4/5/06, Segin <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Well if the game crashes, even quitting, then it's likely not going to
> restore the resolution no matter what.
>
>
> Ahh, that's where the irony is, it does restore resolution.
>
Oh, I guess it's not crashing then! =p
Haha well where t
Jesse Allen wrote:
On 4/5/06, Segin <[EMAIL PROTECTED]> wrote:
Jesse Allen wrote:
On 4/5/06, Molle Bestefich <[EMAIL PROTECTED]> wrote:
These lines could explain why Starcraft is unable to switch to fullscreen:
err:xrandr:X11DRV_XRandR_GetCurrentMode In unknown mode,
returnin
On 4/5/06, Segin <[EMAIL PROTECTED]> wrote:
> Jesse Allen wrote:
> On 4/5/06, Molle Bestefich <[EMAIL PROTECTED]> wrote:
>
>
> These lines could explain why Starcraft is unable to switch to fullscreen:
>
> err:xrandr:X11DRV_XRandR_GetCurrentMode In unknown mode,
> returning default
> fixme:xrand
On Wed, 2006-04-05 at 13:59 -0400, Segin wrote:
> Jesse Allen wrote:
> I don't know... All I get is this AFTER StarCraft quits:
>
> X Error of failed request: BadDrawable (invalid Pixmap or Window
> parameter)
> Major opcode of failed request: 70 (X_PolyFillRectangle)
> Resource id in fail
Jesse Allen wrote:
On 4/5/06, Molle Bestefich <[EMAIL PROTECTED]> wrote:
These lines could explain why Starcraft is unable to switch to fullscreen:
err:xrandr:X11DRV_XRandR_GetCurrentMode In unknown mode, returning default
fixme:xrandr:X11DRV_XRandR_SetCurrentMode Cannot change sc
On 4/5/06, Molle Bestefich <[EMAIL PROTECTED]> wrote:
> These lines could explain why Starcraft is unable to switch to fullscreen:
>
> err:xrandr:X11DRV_XRandR_GetCurrentMode In unknown mode, returning default
> fixme:xrandr:X11DRV_XRandR_SetCurrentMode Cannot change screen BPP from 16 to
> 8
> fi
On 05/04/06, Molle Bestefich <[EMAIL PROTECTED]> wrote:
> I seem to remember that BPP cannot be changed _at all_ with XRandR, is
> this correct?
Yes.
These lines could explain why Starcraft is unable to switch to fullscreen:
err:xrandr:X11DRV_XRandR_GetCurrentMode In unknown mode, returning default
fixme:xrandr:X11DRV_XRandR_SetCurrentMode Cannot change screen BPP from 16 to 8
fixme:xrandr:X11DRV_XRandR_SetCurrentMode Cannot change screen BPP f
22 matches
Mail list logo
