Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
- Subject: Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
- From: Jeremy Huddleston <email@hidden>
- Date: Mon, 29 Sep 2008 23:49:56 -0700
On Sep 29, 2008, at 22:59, Cameron Simpson wrote:
Hmm... this is going to be a pickle to deal with. We're reporting
the full screen size because that is what is going to be used when
we enable full screen support in the WM or when we enable rooted
mode (also fullscreen without the mac menu bar)...
But... until then, that area is not a reasonable thing to offer.
Could it not be offered please?
As I mentioned, I will be fixing this in due time.
( BTW, you remark on a web page somewhere that the full screen code
is lost
in the old Apple code, not available. Maybe you should contact the
author
of Chicken-of-the-VNC, which has a working togglable full screen
mode. He
may be able to supply the necessary Apple fu.
)
That's not exactly the case. It's not a matter of "how do we enable
fullscreen mode"... that's easy. It's a matter of how do we get that
to work with a rooted window in X11 and keep existing windows and
input working as expected.
As remarked, the stock X11 didn't offer this. I'm encountering this
problem by proxy today; my GF runs X11 with icewm and today upgraded
her Mac from 10.5.4 to 10.5.5, and this probably also updated X11.
Yes. You can get more info about what exactly was updated on the
xquartz.macosforge.org front page.
Before the update, icewm put the task bar just below the apple menu
bar and
kept windows below it.
After the upgrade, the task bar is under the apple menu bar and cannot
be used. Likewise, maximising a window puts its title bar under the
menu
bar, and then things are very bad indeed.
yes. This is because before we had in place a hack that didn't work
very well to get around this problem. I removed that hack when we
implemented the multi-monitor hotswapping code since the updated code
fixed the situation (except for your case with other WMs that I'm now
aware of).
I am speculating that the Apple X11 either didn't offer the menu bar
area,
_or_ that it presented a client with EWMH settings to "claim" that
area.
Probably the former.
No, it's neither ... it was a kludge... check out git.freedesktop.org
if you're really curious. I know quartz.c was changed as part of this
cleanup, so you can look in the log for that file to narrow it down...
search for "monitor" in the log comments.
I'll probably have to add in some logic for the transition between
these phases much like when a new monitor is plugged in... hmm...
I was thinking that because you can resize the presented area on a
monitor plug, this kind of thing should in fact be pretty easy.
yes, it should... but there are other higher priority issues at the
moment, so please be patient.
xorg.conf is for the xorg/xfree86 DDX, not the XQuartz DDX. Your
preferences are mostly in X11->Preferences (with a few extras that
you
can read about in the XQuartz man page that you need to set directly
using defaults).
But... none of those give control of X11's drawable area.
Right... that's because the drawable area should be "everything" and
there's no need for an option once this bug is fixed.
Could you at least present a pref giving a "preferred drawable area"
or something like that. It would make things work for several people
from the sound of it.
No. It would be preference clutter and is irrelevant once this bug is
properly fixed.
Yeah, kinda... more like I didn't predict people trying to use X11 on
OSX this way quite yet (I wanted some breathing time with a working
quartz-wm X11 before people tried things like other WM/SMs).
Regretably, there were people using X11 with other WMs well back in
the
Tiger days.
Yes, but I'm primarily focused on getting things working as best I can
with quartz-wm as best I can first and foremost, and if that
introduces a small regression in other WMs that aren't reported for 5
months, then I'm sorry. I will certainly fix it now that I know about
it, but you need to have a bit of patience as there are some other
pressing matters ahead of it right now... but I do expect that it will
make it into 2.3.2 (a bug report has been filed at http://xquartz.macosforge.org
, right?)
--Jeremy
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden