ahhh… thanks! thats great.. didn't know it was libXplugin. Just used native libXplugin on the system and the windows look fine… was using a version from 10.5. This is because "WineskinX11" (my build of Xquartz) is portable and moves from location to location bundled inside an app, and doesn't use the system X11 files, so I had to modify all kinda libraries to get things working perfectly…. but since I made it all up as I went without understanding why some things worked and didn't work, libXplugin was a bit sloppy :-) On Sep 15, 2011, at 1:56 PM, Jeremy Huddleston wrote:
On Sep 15, 2011, at 7:02 AM, doh123 wrote:
A quick question…
What (or where in the code) determines what quartz-wm window decorations look like. Meaning… where does it determine if it looks like 10.5, or 10.6 or 10.7?
That's in the libXplugin internals. On 10.6 and later, it is using the HITheme APIs from Carbon's HIToolbox.
I ask because in Wineskin, I use primarily a 10.5 build, and running it on 10.6 or 10.7, the windows still look like 10.5 windows.
On 10.5, you should notice that the windows look like 10.4 windows.
I thought it was just something to do with quartz-wm, but even using /usr/bin/quartz-wm on a 10.7 machine, the windows still look like 10.5.
Can you provide a screenshot comparing an xterm window to Terminal.app?
If I knew where specifically or in what library it is set, I can modify the code to work differently on different OS versions… or at least link to the correct libraries on the machine if they are available.
--- Jeremy Huddleston
Rebuild Sudan - Board of Directors - http://www.rebuildsudan.org
Berkeley Foundation for Opportunities in Information Technology - Advisory Board - http://www.bfoit.org
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev