December 2007 - Xquartz-dev - lists.macosforge.org

Re: [Xquartz-dev] LSBackgroundOnly at runtime
by Kyle McKay 06 Dec '07

06 Dec '07

Jeremy, I was going to post the below suggestion, but someone beat me to it. I have been playing around with a simple test application and that does exactly this. It uses this key in the Info.plist <key>LSBackgroundOnly</key> <string>1</string> Which is not exactly the same, but I expect <true/> to be just as good. Then it does exactly what your code below does and a Dock icon always appears after calling TransformProcessType. If I comment out the TransformProcessType call there's no Dock icon. Are you calling TransformProcessType as early as possible? Also keep in mind that when you're started by the finder, you'll get this extra argument that starts with -psn_. But it seems like you could call TransformProcessType immediately in main if argc<=1 or argc==2 and argv[1] starts with "-psn_" or maybe I have the sense of that test backwards, but you get the idea about the extra argument you have to account for. Kyle On Dec 5, 2007, at 05:00, xquartz-dev-request(a)lists.macosforge.org wrote: > From: Jeremy Huddleston <jeremyhu(a)berkeley.edu> > Date: December 4, 2007 23:04:27 PST > To: Developer talk about Xquartz <xquartz-dev(a)lists.macosforge.org> > Subject: Re: [Xquartz-dev] LSBackgroundOnly at runtime > Reply-To: Developer talk about Xquartz <xquartz- > dev(a)lists.macosforge.org> > > > Hrm... I tried this (needs to be in a separate C file due to type > conflicts): > > #include <ApplicationServices/ApplicationServices.h> > > int moveToForeground() { > ProcessSerialNumber psn = { 0, kCurrentProcess }; > OSStatus returnCode = TransformProcessType(& psn, > kProcessTransformToForegroundApplication); > if( returnCode == 0) { > //SetFrontProcess(&psn); > } > return (int)returnCode; > } > > and called moveToForeground() before server_main(). this was added > to Info.plist: > <key>LSBackgroundOnly</key> > <true/> > > > returnCode was 0 (success), but the app didn't show up in the > dock. I'm thinking this just won't work and I'm willing to settle > with the current situation for now (since it's still better than > before)... but still not optimal... > > --Jeremy

3 4

Re: [Xquartz-dev] LSBackgroundOnly at runtime
by Jeremy Huddleston 05 Dec '07

05 Dec '07

No, it was definitely picking up the LSBackgroundOnly. The problem was with it not coming into the foreground. I'll maybe come back to it later, but I don't enjoy banging my head on my keyboard... they break too easily... On Dec 4, 2007, at 23:49, Nicholas Riley wrote: > You wrote: >> returnCode was 0 (success), but the app didn't show up in the dock. >> I'm thinking this just won't work and I'm willing to settle with >> the current situation for now (since it's still better than >> before)... but still not optimal.. > You need to touch the bundle directory (touch .../X11.app) after > setting LSBackgroundOnly, otherwise Launch Services may not pick it > up. That could be the issue. > > I know TransformProcessType works, as Tcl and Python (at least) use > it so you can run their command-line versions yet they can spawn a > dock icon if necessary when they start doing GUI stuff. So it's > probably worth sticking with a little more... > > -- > Nicholas Riley <njriley(a)uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley > > >

1 0

[Xquartz-dev] code cleanup, combining quartzBlah.c and darwinBlah.c, etc, etc...
by Jeremy Huddleston 05 Dec '07

05 Dec '07

Unless anyone has an objection, I'm going to spend some time going through, cleaning up header files, adding documentation where I think it's appropriate, and moving around code between files to clean up our layout. I'll probably kill off cr and fullscreen while I'm at it. I need to get a handle on the startup code and events system, and there is alot of cruft getting in the way of my understanding... hopefully by cleaning up some of this stuff, I can clear out dead code and streamline our event pipe a bit. Ben, what were the main changes you needed to do to get events working right in the 1.4 server? I haven't really looked at the changes between the two versions, but I did notice that the X11Application.m darwinEvents.c in 1.2 won't work dropped into 1.4. --Jeremy

2 1

RE: [Xquartz-dev] code cleanup, combining quartzBlah.c and darwinBlah.c, etc, etc...
by Nathaniel Gray 05 Dec '07

05 Dec '07

For some reason I got a postfix error when I tried to send this the last time. Hopefully it's not a dupe... ---------- Forwarded message ---------- From: Nathaniel Gray <n8gray(a)gmail.com> Date: Dec 4, 2007 1:49 AM Subject: Re: [Xquartz-dev] code cleanup, combining quartzBlah.c and darwinBlah.c, etc, etc... To: Developer talk about Xquartz <xquartz-dev(a)lists.macosforge.org> On Dec 3, 2007 11:28 PM, Jeremy Huddleston <jeremyhu(a)berkeley.edu> wrote: > Unless anyone has an objection, I'm going to spend some time going > through, cleaning up header files, adding documentation where I think > it's appropriate, and moving around code between files to clean up our > layout. I'll probably kill off cr and fullscreen while I'm at it. I > need to get a handle on the startup code and events system, and there > is alot of cruft getting in the way of my understanding... hopefully > by cleaning up some of this stuff, I can clear out dead code and > streamline our event pipe a bit. I'd say killing off fullscreen is probably not a great idea since we do want to get it working at some point. I'm also not thrilled about killing off cr, since I think it's actually potentially a better way of doing the server. It's not like you really have to *look* in those dirs... One thing I did to aid my own comprehension of the code was to make a dummy Xcode project and just import "useful" directories. That way you can filter out all the stuff you don't care about, use Xcode's "jump to definition" features and so on. Very handy. Cheers, -n8 -- >>>-- Nathaniel Gray -- Caltech Computer Science ------> >>>-- Mojave Project -- http://mojave.cs.caltech.edu --> -- >>>-- Nathaniel Gray -- Caltech Computer Science ------> >>>-- Mojave Project -- http://mojave.cs.caltech.edu -->

3 2

LSBackgroundOnly at runtime
by Jeremy Huddleston 05 Dec '07

05 Dec '07

So, I don't have much experience with launch-services, open-step, or cocoa... so I'm going to be needing some crutches for a while... I think I figured out what I need to do to eliminate the second dock icon. I need to manage the foreground/background-ness of the application such that the launcher behaves as if LSBackgroundOnly=true and the server behaves as if LSBackgroundOnly=false. How does one go about changing this at runtime to push a background app into the foreground or visa-versa? It looks like NSApplication.hide() isn't right... that just causes the windows to hide, not push the app into the background... any help? Thanks, Jeremy

3 5

problem building xorg-server-1.3.0-apple2?
by Ben Byer 05 Dec '07

05 Dec '07

Hopefully I'm just on crack, but I'm getting this when trying to build this: make[3]: *** No rule to make target `quartz/libXquartz.a', needed by `Xquartz'. Stop. I haven't had a chance to dig into it. Jeremy, does that look at all familiar? -- Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer

2 5

Re: Fast User Switching Problem
by Jeremy Huddleston 05 Dec '07

05 Dec '07

/punt to Ben. I included your xcb changes in the package... looks like something's not working as expected... On Dec 4, 2007, at 19:52, Ken Preslan wrote: > Hi! > > I was using the x11_update.sh script from http://www.x.org/wiki/XDarwin > . > (I ran it around 11/25, whatever version that was.) That worked fine > for me. > > I just upgraded to 2.1.0.1 and now I'm having problems with fast user > switching. The first user that starts X11 works just fine. When I > switch to another user and try to start X11 there, the X server starts > and quits over and over again. In Console, I see error messages like: > > 12/4/07 9:29:33 PM org.x.X11[207] Invalid MIT-MAGIC-COOKIE-1 keyXlib: > connection to ":0.0" refused by server > 12/4/07 9:29:33 PM org.x.X11[207] Xlib: Invalid MIT-MAGIC-COOKIE-1 key > 12/4/07 9:29:33 PM org.x.X11[207] Fatal server error: > 12/4/07 9:29:33 PM org.x.X11[207] Server is already active for > display 0 > 12/4/07 9:29:33 PM org.x.X11[207] If this server is no longer > running, > remove /tmp/.X0-lock > 12/4/07 9:29:33 PM org.x.X11[207] and start again. > 12/4/07 9:29:33 PM org.x.X11[207] AbortDDX > 12/4/07 9:29:33 PM org.x.X11[207] Quitting XQuartz... > 12/4/07 9:29:34 PM org.x.X11[207] Xlib: connection to ":0.0" refused > by > server > 12/4/07 9:29:34 PM org.x.X11[207] Xlib: Invalid MIT-MAGIC-COOKIE-1 key > > So, it seems like second user isn't getting the message to use display > :1. > > Little help? > > Thanks! > > (I'm running the latest Leopard on a PPC, btw.) > > -- > Ken Preslan <ken(a)preslan.org> > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > X11-users mailing list (X11-users(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop.org > > This email sent to jeremyhu(a)freedesktop.org

1 0

RFC: Combining both X11.apps into one
by Jeremy Huddleston 05 Dec '07

05 Dec '07

I just committed a patch that combines both X11.apps into one application and intelligently determines what to do at execution. See http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commit;h=0284b3631a4c50… I know I was confused about the two different versions, so I thought this might help out the situation. If you try it out, make sure you grab the updated LaunchAgent plist (also in the commit) and restart first. Note that this hasn't fixed the "extra dock icon" problem or anything like that. I hope to figure out a solution to that as I work on this refactoring of the startup process, but I'm not there yet. As an end goal, I'd like X11.app to *really* be Xquartz rather than fork to execute it. I think that might make it a bit cleaner and clear up any weird double-icon problems. Comments and feedback on this would be appreciated... especially if you are partial to having this division, I'd like to hear from you. Thanks, Jeremy

3 4

Re: Making Xquartz work with the Dock (and XDMCP)
by Ben Byer 03 Dec '07

03 Dec '07

On Dec 1, 2007, at 4:28 PM, Kyle McKay wrote: > Ben, > > I have been using the latest versions of the Xorg X11 for 10.5.x > that you have posted at <http://people.freedesktop.org/~bbyer/x11app/ > >. They have resolved a whole bunch of problems -- wireshark works > for me now, kdevelop runs without anymore unreadable garbage in > scrolling windows and the yellow cursor problem is gone. Thank you > for posting these. > > Hopefully fullscreen will start working someday soon as well. > > But the subject of this post is Xquartz, the Dock and XDMCP. I am > now successfully running Xquartz directly from a shell prompt like > this: > > Xquartz :1 -query remote.host.name -from ppp.if.address +xinerama - > once > > (where remote.host.name is the host I tested with and ppp.if.address > is the IPv4 address of my end of the VPN ppp connection I brought up > so I could test). > > Works fine. An icon shows up in the Dock as soon as I start > Xquartz. I do have to click on it or Command-Tab to it to bring it > forward at which point I can log in to the remote host via its login > dialog. > > So what you need to do to make this work is add a 'plst' 0 resource > to Xquartz. (See <http://developer.apple.com/technotes/tn/ > tn2013.html> for info about this.) > Awesome! Does this end up using the actual X11.app icon, or just the generic "exec" icon? I have another solution from the Dock team, that involves adding this code to X11ApplicationMain: + ProcessSerialNumber psn = { 0, kCurrentProcess }; + fprintf(stderr, "Calling TransformProcessType\n"); + TransformProcessType(&psn, kProcessTransformToForegroundApplication); + SetFrontProcess(&psn); It produces a dock icon (although only the generic one), but when I actually try to run xterm, as soon as I click on it, it crashes here: Thread 1 Crashed: 0 Xquartz 0x0002799d RootlessNativeWindowMoved + 16 (rootlessWindow.c:144) 1 Xquartz 0x000186ee DarwinModeProcessEvent + 798 (quartz.c:471) 2 Xquartz 0x000057ce ProcessInputEvents + 1930 (darwinEvents.c:409) 3 Xquartz 0x0007ddcf Dispatch + 117 4 Xquartz 0x000995e5 main + 1921 5 Xquartz 0x00019f24 server_thread + 59 6 libSystem.B.dylib 0x9672b075 _pthread_start + 321 7 libSystem.B.dylib 0x9672af32 thread_start + 34 It sounds like your solution gives a better result (and without crashing!), but Apple is trying to deprecate resource forks in general and I'm not sure I'd actually be able to ship a fix that required adding a resource fork. :( -- Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer

3 4

Re: minor formatting bug in Xquartz man page
by Peter O'Gorman 03 Dec '07

03 Dec '07

Jeremy Huddleston wrote: > I honestly know next to nothing about writing man pages. If someone > wants to submit a patch (either in this list or as a bug report on > xquartz.macosforge.org) I'd be very appreciative. > > Thanks, > Jeremy > >> This is great, too, but there is a minor formatting bug: at the end of >> the page, the references >> X(__miscmansuffix__) >> __vendorversion__ >> should be replaced by the man suffix and the vendor, respectively. Currently the manpage is copied directly from Xquartz.man in hw/darwin to the installed Xquartz.1, it looks like it should have a sed done on it. in Makefile.am put man1_MANS = Xquartz.1 Xquartz.1: Xquartz.man <TAB>sed -e "s!__vendor_version__!$(VENDOR_MAN_VERSION)!g" -e "s! __miscmansuffix__!1!g" < Xquartz.man > Xquartz.1 Should work, but untried. Peter -- Peter O'Gorman http://pogma.com

1 0