Apache OpenOffice (AOO) Bugzilla – Issue 25248
Fullscreen Presentation should use *physical* resolution of dpy
Last modified: 2013-02-07 22:35:38 UTC
This applies to any System running X11, at least when using XFree86. When displaying a presentation in fullscreen mode, Impress uses the virtual resolution. My laptop does 1280x1024, but our projector only does 1024x768. For now, I have to restart the X11 Server to run at 1024x768 virtual *and* virtual (ie, no panning) to be able to do a presentation. It would be nice to make Impress look up the *current* *physical* resolution of the X11 Server, and use that for a fullscreen presentation. For examples, see the hacks of xscreensaver, which always display in the current physical resolution.
See also http://www.openoffice.org/issues/show_bug.cgi?id=18184
Reassigned to Bettina.
I was faced with this issue yesterday and did some research on it. I think, that this issue is actually a window manager issue. It seems that my good old sawfish does not handle RandR events correctly, or does not handle them at all. Unfortunately sawfish's development is stalled since some months, so I decided to give metacity a try. Metacity seems to work fine, even resolution changes during(!) a fullscreen presentation are handled correctly. However, I noticed some interesting things in my experiments with sawfish. If I started OOo Impress, then changed screen resolution and started the fullscreen presentation after the resolution change, the slide show was displayed at the resolution used when starting Impress. (e.g. when the initial resolution was smaller than the new one, the slides are displayed in the upper left corner of the screen; when the initial resolution was bigger than the new one, then the slides do not fit the screen) So, it seems to me, that OOo Impress can detect the correct screen resolution, even when the window manager is buggy, but it does at startup instead of when the fullscreen slide show is started. Hence, I think that a workaround for faulty window managers would not be difficult (and I could switch back to my trusty, well configured sawfish).
To grep the issues easier via "requirements" I put the issues currently lying on my owner to the owner "requirements".