[openbox] Window Placement in MergedFB (not Xinerama) Mode with ATI Radeon 7500
Adam Kessel
adam at rosi-kessel.org
Tue May 25 14:38:12 EDT 2004
On Tue, May 25, 2004 at 08:15:22PM +0200, Mikael Magnusson wrote:
> On Tue, 25 May 2004, Adam Kessel wrote:
> > Is there any way to tell OpenBox to always open child windows on the same
> > screen as the parent window in MergedFB mode? Does OpenBox even know
> > what MergedFB mode is?
> Most likely not, I don't.
http://www.botchco.com/alex/radeon/mergedfb/cvs/DRI/final/radeon.4.html
"This enables merged framebuffer mode. In this mode you have a single
shared framebuffer with two viewports looking into it. It is similar
to Xinerama, but has some advantages. It is faster than Xinerama, the
DRI works on both heads, and it supports clone modes. Merged
framebuffer mode provides two linked viewports looking into a single
large shared framebuffer. "
I am using pseudo-Xinerama mode, described as:
Since merged framebuffer mode does not use Xinerama, apps are not
able to intelligently place windows. Merged framebuffer mode provides
its own pseudo-Xinerama. This allows Xinerama compliant applications
to place windows appropriately. There are some caveats. Since merged
framebuffer mode is able to change relative screen sizes and
orientations on the fly, as well has having overlapping viewports,
pseudo-Xinerama, might not always provide the right hints. Also many
Xinerama compliant applications only query Xinerama once at startup;
if the information changes, they may not be aware of the change. If
you are already using Xinerama (e.g., a single head card and a
dualhead card providing three heads), pseudo-Xinerama will be
disabled.
If pseudo-Xinerama works as described, it seems like OpenBox's Xinerama
support should place windows in the right place--right? Any way to
figure out what's actually going on?
--
Adam Kessel
http://adam.rosi-kessel.org
More information about the openbox
mailing list