Could you please file a bug for this... I've actually never used that feature, so I didn't even know to look for it. I'll see if I can get it in there for 2.2.1... there are a couple of more important things I'd like to look at before the much-needed-update to 2.2.0. --Jeremy On Apr 1, 2008, at 08:04, mick.mueck@comcast.net wrote:
G'Day Jeremy,
I just tried out 2.2.0_rc2 - this is my first experience with 2.2, I've never tried rc1. Anyway, I made myself a bunch of overlapping windows and tried expose - it all seemed to work fine. Thank you :-). Then just for the heck of it I tried to move a background window by command-dragging on the title bar. In regular OS X the front window maintains focus when you do this. In X11 the dragged window ends up having the focus. Probably not a big deal, but figured you might want to know...
Mick.
-------------- Original message ---------------------- From: Jeremy Huddleston <jeremyhu@apple.com>
_______________________________________________ Sorry for the short email... tired... yawn...
This fixes all the issues reported with 2.2.0_rc1 (exposé F9 bringing all to front, preferences-only-once, and the app-defaults files). Please test.
http://xquartz.macosforge.org/downloads/X11-2.2.0_rc2.pkg _______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list (X11-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop.org
This email sent to jeremyhu@freedesktop.org
Hi. I had a little time so I have performed few test of rc2. Here are results: 1) OpenOffice doesn't work with rc2 2) Every wine/windows program outputs this error: err:wgl:has_opengl glx_version is 1.2 and GLX_SGIX_fbconfig extension is unsupported. Expect problems. err:wgl:has_opengl glx_version is 1.2 and GLX_SGIX_fbconfig extension is unsupported. Expect problems. 3) glxgears show 2200 FPS but the wheels doesn't move at all. If you click on a window they start to move but then then you are only able to get 550 FPS. Regards Michal. On Tue, Apr 1, 2008 at 5:15 PM, Jeremy Huddleston <jeremyhu@apple.com> wrote:
Could you please file a bug for this... I've actually never used that feature, so I didn't even know to look for it. I'll see if I can get it in there for 2.2.1... there are a couple of more important things I'd like to look at before the much-needed-update to 2.2.0.
--Jeremy
On Apr 1, 2008, at 08:04, mick.mueck@comcast.net wrote:
G'Day Jeremy,
I just tried out 2.2.0_rc2 - this is my first experience with 2.2, I've never tried rc1. Anyway, I made myself a bunch of overlapping windows and tried expose - it all seemed to work fine. Thank you :-). Then just for the heck of it I tried to move a background window by command-dragging on the title bar. In regular OS X the front window maintains focus when you do this. In X11 the dragged window ends up having the focus. Probably not a big deal, but figured you might want to know...
Mick.
-------------- Original message ---------------------- From: Jeremy Huddleston <jeremyhu@apple.com>
_______________________________________________
Sorry for the short email... tired... yawn...
This fixes all the issues reported with 2.2.0_rc1 (exposé F9 bringing all to front, preferences-only-once, and the app-defaults files). Please test.
http://xquartz.macosforge.org/downloads/X11-2.2.0_rc2.pkg _______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list (X11-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop.org
This email sent to jeremyhu@freedesktop.org
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
On Apr 5, 2008, at 07:11, Michał Majchrowicz wrote:
Hi. I had a little time so I have performed few test of rc2. Here are results: 1) OpenOffice doesn't work with rc2
Nor does it work with 2.1.4. It's OOo's fault. They do some bad logic to set $DISPLAy which they shouldn't.
2) Every wine/windows program outputs this error: err:wgl:has_opengl glx_version is 1.2 and GLX_SGIX_fbconfig extension is unsupported. Expect problems. err:wgl:has_opengl glx_version is 1.2 and GLX_SGIX_fbconfig extension is unsupported. Expect problems.
That is expected / better than 2.1.4 in which they all froze
3) glxgears show 2200 FPS but the wheels doesn't move at all. If you click on a window they start to move but then then you are only able to get 550 FPS.
They are probably moving at a rate that prevents you from seeing it (ie, the rendered image is exactly the same because they moved, but you can't tell because of rotational symmetry). They are moving fine here. Thanks for testing =) --Jeremy
Hi. You didn't understand my report when I click on the glxgears or move a window the wheels DO move but they move at rate of 500 FPS. It shouldn't be this way :) Regards Michal. On Sat, Apr 5, 2008 at 5:20 PM, Jeremy Huddleston <jeremyhu@berkeley.edu> wrote:
On Apr 5, 2008, at 07:11, Michał Majchrowicz wrote:
Hi. I had a little time so I have performed few test of rc2. Here are results: 1) OpenOffice doesn't work with rc2
Nor does it work with 2.1.4. It's OOo's fault. They do some bad logic to set $DISPLAy which they shouldn't.
2) Every wine/windows program outputs this error: err:wgl:has_opengl glx_version is 1.2 and GLX_SGIX_fbconfig extension is unsupported. Expect problems. err:wgl:has_opengl glx_version is 1.2 and GLX_SGIX_fbconfig extension is unsupported. Expect problems.
That is expected / better than 2.1.4 in which they all froze
3) glxgears show 2200 FPS but the wheels doesn't move at all. If you click on a window they start to move but then then you are only able to get 550 FPS.
They are probably moving at a rate that prevents you from seeing it (ie, the rendered image is exactly the same because they moved, but you can't tell because of rotational symmetry). They are moving fine here.
Thanks for testing =)
--Jeremy _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
Micha? Majchrowicz wrote:
Hi. You didn't understand my report when I click on the glxgears or move a window the wheels DO move but they move at rate of 500 FPS. It shouldn't be this way :)
Here is what I see: I place the glxgears window outside of, but close to the Terminal.app window from which I started glxgears. The wheels are moving smoothly, and when the glxgears window has focus, I get a reported 3458 FPS. When I click on the Terminal.app window to give it focus, the visible movement of the wheels is exactly the same as before, but I get 59 FPS, that is, over fifty times slower! My conclusion: What you see in the window has absolutely nothing to do with the reported FPS, and the latter depends in an extreme way on the (geometrical) environment of the glxgears window. -- Martin
On Apr 5, 2008, at 12:26 PM, Martin Costabel wrote:
Micha? Majchrowicz wrote:
Hi. You didn't understand my report when I click on the glxgears or move a window the wheels DO move but they move at rate of 500 FPS. It shouldn't be this way :)
Here is what I see: I place the glxgears window outside of, but close to the Terminal.app window from which I started glxgears. The wheels are moving smoothly, and when the glxgears window has focus, I get a reported 3458 FPS. When I click on the Terminal.app window to give it focus, the visible movement of the wheels is exactly the same as before, but I get 59 FPS, that is, over fifty times slower! My conclusion: What you see in the window has absolutely nothing to do with the reported FPS, and the latter depends in an extreme way on the (geometrical) environment of the glxgears window.
The Terminal.app window casts a shadow. It's larger than you might think at first. When this window is above the glxgears window, the Window Server has to composite the shadow onto the glxgears window. The Window Server deliberately restricts such operations to once per monitor refresh, which is usually around 60Hz for LCDs. This can be disabled with Quartz Debug.app. -Ken
participants (5)
-
Jeremy Huddleston
-
Jeremy Huddleston
-
Ken Thomases
-
Martin Costabel
-
Michał Majchrowicz