Implementing Xinerama

[Judd Tracy]

I have been trying to get a very simple Xinerama implementation working for
wine, but am having some problems.  My approach was to just query the system
for the screens that make up the display and only report the resolution of
the first display with the offset of 0+0.  The resolution detection part of
the code seems to be working as I can see looking through the traces, but
every time the app comes up full screen it still stretches across both
screens.  I can see it enumerating the displays (there is only one) and
finding the correct resolution, but don't understand why it still comes up
across both screens.

I was hoping someone could explain what else I need to do attempt to get
this working.  I am using wine version 0.9.11 which I have applied a patch
to work around the WorldOfWarcraft picking bug.  The Xinerama display that I
am using has a resolution of 2560 x 1024 and when I query the screens I get
Screen 0: 0+0+1280x1024 and Screen 1: 1280+0+1280x1024.  When I detect the
screens I only put in one resolution which is the one with offset (0+0).  So
for my system there should be only one resolution to choose from.  I base my
code off the structure of XRandR so it should be for the most part correct.
If anyone could help it would be appreciated.

Judd Tracy

[Vitaliy Margolen]

Thursday, April 27, 2006, 7:38:52 PM, Judd Tracy wrote:
> I have been trying to get a very simple Xinerama implementation
> workingfor wine, but am having some problems.  My approach was to
> justquery the system for the screens that make up the display and
> onlyreport the resolution of the first display with the offset of0+0. 
> The resolution detection part of the code seems to beworking as I can
> see looking through the traces, but every time the appcomes up full
> screen it still stretches across both screens.  Ican see it enumerating
> the displays (there is only one) and finding thecorrect resolution, but
> don't understand why it still comes up acrossboth screens.
> I was hoping someone could explain what else I need to do attempt
> toget this working.  I am using wine version 0.9.11 which I haveapplied

For starters don't send html to the list.
You are looking in the wrong direction here. Even if Wine could detect
separate monitors and work with them properly (all the DSIPLAY0 stuff)
you still would have a problem on the WM side. You see Wine does not
maximizes itself - WM does. Wine does not talk to WMs except few
rudimentary things. You will need to extend that so Wine could tell WM
how it should be maximized.

Vitaliy

[Francois Gouget]

On Thu, 27 Apr 2006, Vitaliy Margolen wrote:
[...]
> You see Wine does not
> maximizes itself - WM does. Wine does not talk to WMs except few
> rudimentary things. You will need to extend that so Wine could tell WM
> how it should be maximized.

Does this mean we would need a change in the WM 'API'? If so, could you 
describe the issue in the Wiki?

http://wiki.winehq.org/IntegrationProjects

-- 
Francois Gouget <fgouget(a)free.fr>              http://fgouget.free.fr/
               Linux: Because rebooting is for adding new hardware

[Mike Hearn]

On Fri, 28 Apr 2006 19:21:55 +0200, Francois Gouget wrote:
> Does this mean we would need a change in the WM 'API'? If so, could you 
> describe the issue in the Wiki?

This was already fixed by a patch I wrote long ago but that was never
merged. It was done to fix IE but bugs in our rebar control prevented it
working properly. Google for my name + fullscreen patch to find it ...

thanks -mike