2.6.0_alpha2 pulls in all the changes that went into 2.5.3 (some of which weren't in 2.6.0_alpha1), pulls in upstream changes from 1.9 RC6, and has a bunch of additional work on RandR which addresses the crash in alpha1 and better integrates RandR with the legacy rootless/fullscreen mode switching. It doesn't yet Capture/Release the screen like it should. I spent about 5 minutes working on that before the flight attendant made me turn off the laptop, and it was giving me issues, so it'll have to wait until next time. You can just check for updates or grab it here: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.0_alpha2.dmg Thanks, Jeremy
just a question... is RANDR supposed to be working on 10.5 yet? I did a Macports install of xorg-server-devel on 10.5 and xrandr doesn't report back anything unless I have multiple monitors, then just the single monitor full size... but with a single monitor, xrandr doesn't say anything... nothing at all, just type it in and back to the prompt. I didn't want to put in a bug report since the alpha is a 10.6 build I was thinking maybe it wasn't supposed to be working yet. this alpha build is working decently on 10.6 though. On Aug 13, 2010, at 7:57 PM, Jeremy Huddleston wrote:
2.6.0_alpha2 pulls in all the changes that went into 2.5.3 (some of which weren't in 2.6.0_alpha1), pulls in upstream changes from 1.9 RC6, and has a bunch of additional work on RandR which addresses the crash in alpha1 and better integrates RandR with the legacy rootless/fullscreen mode switching. It doesn't yet Capture/Release the screen like it should. I spent about 5 minutes working on that before the flight attendant made me turn off the laptop, and it was giving me issues, so it'll have to wait until next time.
You can just check for updates or grab it here: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.0_alpha2.dmg
Thanks, Jeremy
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Aug 18, 2010, at 14:20, doh123 wrote:
just a question... is RANDR supposed to be working on 10.5 yet? I did a Macports install of xorg-server-devel on 10.5 and xrandr doesn't report back anything unless I have multiple monitors, then just the single monitor full size... but with a single monitor, xrandr doesn't say anything... nothing at all, just type it in and back to the prompt. I didn't want to put in a bug report since the alpha is a 10.6 build I was thinking maybe it wasn't supposed to be working yet. this alpha build is working decently on 10.6 though.
It should be working on 10.4 through 10.6. The multi-monitor case should actually be working "less" because we only are presenting the two legacy modes (rootless and fullscreen). What is xrandr's exit code? ('echo $?' after running it) I think xrandr should always print something... even if RandR isn't available, it'll print: ~ $ xrandr Xlib: extension "RANDR" missing on display ":4.0". RandR extension missing
I've had some inconsistencies with RandR in this version. Usually after a game switches to fullscreen (same as xrandr -s 1) when I press cmd-opt-a the windows will be visible on the rootless window, but once in a while they will not be. In the former case I can not press cmd-opt-a again to return to fullscreen, but in the latter case I can. In alpha1 the windows were always hidden when pressing cmd-opt-a and you had to press it again to show them. I assume that's how it's supposed to be all the time. I haven't had time to work out the details exactly yet, therefore no ticket for now. -- Pelle Johansson 14 aug 2010 kl. 02.57 skrev Jeremy Huddleston:
2.6.0_alpha2 pulls in all the changes that went into 2.5.3 (some of which weren't in 2.6.0_alpha1), pulls in upstream changes from 1.9 RC6, and has a bunch of additional work on RandR which addresses the crash in alpha1 and better integrates RandR with the legacy rootless/fullscreen mode switching. It doesn't yet Capture/Release the screen like it should. I spent about 5 minutes working on that before the flight attendant made me turn off the laptop, and it was giving me issues, so it'll have to wait until next time.
You can just check for updates or grab it here: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.0_alpha2.dmg
Thanks, Jeremy
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Aug 23, 2010, at 00:08, Pelle Johansson wrote:
I've had some inconsistencies with RandR in this version. Usually after a game switches to fullscreen (same as xrandr -s 1) when I press cmd-opt-a the windows will be visible on the rootless window, but once in a while they will not be. In the former case I can not press cmd-opt-a again to return to fullscreen, but in the latter case I can.
If you cmd-opt-a out of a "real" RandR mode, you will return to your default mode (rootless or legacy fullscreen). If legacy fullscreen is your default mode, you will be presented with the OS X Desktop. If you cmd-opt-a out of the legacy fullscreen mode, you will just be presented with the OS X Desktop. It sounds like in one case your game is choosing the legacy mode and in others it is choosing a real mode... I better adjectives. If you run 'xrandr', you will notice two modes with refresh rates of '1' and '2'. These correspond to the legacy non-RandR modes.
In alpha1 the windows were always hidden when pressing cmd-opt-a and you had to press it again to show them. I assume that's how it's supposed to be all the time. I haven't had time to work out the details exactly yet, therefore no ticket for now.
In alpha1, cmd-opt-a behavior wasn't really considered for the RandR modes. The reason for this behavior is to let someone "escape" from a RandR mode set by a crashed application.
23 aug 2010 kl. 20.11 skrev Jeremy Huddleston:
On Aug 23, 2010, at 00:08, Pelle Johansson wrote:
I've had some inconsistencies with RandR in this version. Usually after a game switches to fullscreen (same as xrandr -s 1) when I press cmd-opt-a the windows will be visible on the rootless window, but once in a while they will not be. In the former case I can not press cmd-opt-a again to return to fullscreen, but in the latter case I can.
If you cmd-opt-a out of a "real" RandR mode, you will return to your default mode (rootless or legacy fullscreen). If legacy fullscreen is your default mode, you will be presented with the OS X Desktop.
If you cmd-opt-a out of the legacy fullscreen mode, you will just be presented with the OS X Desktop.
It sounds like in one case your game is choosing the legacy mode and in others it is choosing a real mode... I better adjectives.
Right, I understand how it works now, but it is a little bit weird that it acts differently depending on if a game chose my native resolution or not. Cmd-h acts more consistently though, I guess that's what I should be using if I want to temporarily switch out to read mail etc. Sorry for the late reply, I've been busy... -- Pelle Johansson
No worries... I was expecting that games would NOT choose the "fake" modes because of their unappetizing refresh rates (1.0Hz and 2.0Hz). The "real" modes should have the real refresh rates (like 60Hz). Can you tell me which application this is? I might be able to investigate and see if we can address this by re-ordering the list if it is a common enough problem... On Sep 11, 2010, at 02:46, Pelle Johansson wrote:
23 aug 2010 kl. 20.11 skrev Jeremy Huddleston:
On Aug 23, 2010, at 00:08, Pelle Johansson wrote:
I've had some inconsistencies with RandR in this version. Usually after a game switches to fullscreen (same as xrandr -s 1) when I press cmd-opt-a the windows will be visible on the rootless window, but once in a while they will not be. In the former case I can not press cmd-opt-a again to return to fullscreen, but in the latter case I can.
If you cmd-opt-a out of a "real" RandR mode, you will return to your default mode (rootless or legacy fullscreen). If legacy fullscreen is your default mode, you will be presented with the OS X Desktop.
If you cmd-opt-a out of the legacy fullscreen mode, you will just be presented with the OS X Desktop.
It sounds like in one case your game is choosing the legacy mode and in others it is choosing a real mode... I better adjectives.
Right, I understand how it works now, but it is a little bit weird that it acts differently depending on if a game chose my native resolution or not. Cmd-h acts more consistently though, I guess that's what I should be using if I want to temporarily switch out to read mail etc.
Sorry for the late reply, I've been busy... -- Pelle Johansson
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Hrm, well come to think of it I'm not sure any game has chosen that resolution by default. But I've been changing them, it is the native resolution after all. -- Pelle Johansson 11 sep 2010 kl. 19.25 skrev Jeremy Huddleston:
No worries... I was expecting that games would NOT choose the "fake" modes because of their unappetizing refresh rates (1.0Hz and 2.0Hz). The "real" modes should have the real refresh rates (like 60Hz). Can you tell me which application this is? I might be able to investigate and see if we can address this by re-ordering the list if it is a common enough problem...
On Sep 11, 2010, at 02:46, Pelle Johansson wrote:
23 aug 2010 kl. 20.11 skrev Jeremy Huddleston:
On Aug 23, 2010, at 00:08, Pelle Johansson wrote:
I've had some inconsistencies with RandR in this version. Usually after a game switches to fullscreen (same as xrandr -s 1) when I press cmd-opt-a the windows will be visible on the rootless window, but once in a while they will not be. In the former case I can not press cmd-opt-a again to return to fullscreen, but in the latter case I can.
If you cmd-opt-a out of a "real" RandR mode, you will return to your default mode (rootless or legacy fullscreen). If legacy fullscreen is your default mode, you will be presented with the OS X Desktop.
If you cmd-opt-a out of the legacy fullscreen mode, you will just be presented with the OS X Desktop.
It sounds like in one case your game is choosing the legacy mode and in others it is choosing a real mode... I better adjectives.
Right, I understand how it works now, but it is a little bit weird that it acts differently depending on if a game chose my native resolution or not. Cmd-h acts more consistently though, I guess that's what I should be using if I want to temporarily switch out to read mail etc.
Sorry for the late reply, I've been busy... -- Pelle Johansson
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (4)
-
doh123
-
Jeremy Huddleston
-
Jeremy Huddleston
-
Pelle Johansson