Oh, but please be careful!
AIR, there is a persnickety difference between "localhost:0" and ":0",
I believe, someone correct me if I'm wrong: "localhost:0" hits the
NIC and ":0" is direct rendering. Perhaps you are wondering why you'd
ever want to use the network when you can just set it to :0, and the
answer is: if you are testing software, sometimes you want to test
GLX vs. GL... I hope I'm remembering this correctly.
What I'm saying is, please don't change the usage to be what you think
is the "right" way, i.e., a peculiar Apple-only way, rather do it the
way everyone else does it, or it will actually be harder for a bunch
of us that use multiple platforms to figure out what you thought was
super cool compared to what RHEL does, etc.
On Oct 29, 2007, at 5:58 PM, Mark J. Reed wrote:
On 10/29/07, Ben Byer <email@hidden> wrote:
If I understand what you're suggesting, that is in fact what we're
already doing. We modified libX11.dylib to detect the special launchd
DISPLAY format, and to handle that correctly.
But that's not what Dave was suggesting, IIUC. He was suggesting
that, as a special case, the Apple version of libX11 treat ":0.0" and
other DISPLAY values that normally mean "the local console display"
*as if* they were set to the special launchd format. Assuming it
could figure out where the launchd socket is....
