quartz-wm is usually always the wm.. when its not, there is no wm, but that is not common. All my tests are with quartz-wm, and it doesn't work.
I did narrow it down a bit more… I really hate trying to do bisects… but if I have to I'll eventually do it. Mainly because I cannot ever get xorg-server to build right so I use Macports with a local repo… so I'd have to edit a portfile for each bisect that way. If the Wine program is set to not allow the window manager to decorate/control the Windows, this problem is happening. If I have quartz-wm actually working instead of just loaded… the problem does not seem to be happening. I'd love to leave it on all the time, but quartz-wm always crashes every program going from Windows to fullscreen mode, so its abilities have to be turned off so the programs even work. I wonder how the 1.9 branch brings everything to the front and works right without quartz-wm, yet 1.11.1 requires it… I might never figure it out if I don't take the time to do a bisect, but I've found many other issues affecting me without doing so, but in those I had a clue where to start looking, and the only place I know of with some Mouse handling code is in darwin.c, and it does have some major changes since the 1.9 branch. I guess I'll figure it out eventually :-) On Sep 27, 2011, at 5:07 PM, Jeremy Huddleston wrote: > > On Sep 27, 2011, at 13:38, doh123 wrote: > >> well I went ahead and tried the --pref-domain when started quartz-wm, but it >> changed nothing. I didn't think that was it, because for some things I do, >> quartz-wm is never even ran, and the problem exists the same way. > > Well if quartz-wm isn't your Wm, then you shouldn't expect things like that > to work. quartz-wm is responsible for actually doing those things. X11.app > just changes the preference option and pokes quartz-wm to re-read its > preferences. click-through is a WM option (not just quartz-wm, but WMs in > general). focus on new windows is an Xquartzism that is handled by quartz-wm. > >> I can take the same build and swap between my new 1.11.1 server executable, >> and my older 1.9.3 executable and the problems happens with 1.9.3. All the >> same settings, file libraries everything, only changing the server >> executable. Its driving me crazy… I'm guessing somewhere between the two >> something major changed that doesn't affect normal launching of the server, >> but with the weird way I launch it, its having a problem. I'm just not sure >> where in the source to actually look for where this would be handled so if I >> can find something to modify to fix it, then I will. >> >> Those last 3 patches are the only ones I used to make a "stock" build in >> which the problem appears. Since I already have some of my own patches that >> will go on for a final build, I do not mind if I can modify something in the >> source to fix the problem. > > Well I dunno what could be doing this. If 1.9.x is working for you, then > you're in luck because we were living on master well before that. Your best > bet is to first test 1.10.4 then 1.10.0, then start bisecting along master > between 1.10.0 and either 1.9.0 or 1.11.0. git-bisect is your friend. > > > > > _______________________________________________ > 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
