I have tried this and it doesn't work. You can see ion actively reorganising the applets and getting them in the wrong order.
On Sun, 18 Jul 2004 12:34, Michael Alexander Hamburg wrote: > It all depends on the order in which they get their windows up, which > depends on the size of the app and the complexity of its startup, as > well as other things like disk latencies and buffer cache. > > The simple solution is to make your .xinitrc launch ion first, then > launch the dockapps in order with .2-second (or longer if necessary) > pauses in between. My rather more complex solution is to have a > separate script do this so that it doesn't block the main one. > > My startup script is: > > ######################################## > # this probaly isn't necessary every time > xrdb .Xresources > > # launch ion and remember its PID for later > /usr/X11R6/bin/ion & > IONPID=$! > > # give ion some time to launch > sleep 1 > xterm & > > # This script launches dockapps with .2 second delays > # > # Launch wmblueclock, wmbluecpu, wmmemfree, wmfire > # with appropraite arguments; record their PIDs. > # That way, a later call to dock clock cpu mem sun fire > # can kill them all and relaunch in the right order. > # > # You can replace this with > # wmblueclock &; sleep .2 > # wmbluecpu &; sleep .2 > # ... > ~/bin/dock clock cpu mem fire & > > # hide the mouse after 5 seconds of inactivity > unclutter & > > # in case I spawn a WFloatWS > xsetroot -solid Grey30 > > # block on the saved PID > wait $IONPID > ######################################### > > Your paths may very. It would be kind of nice if there were a way to > rearrange things in-dock, so that I wouldn't need such a complex > script to add and remove things, but it's not a big deal to kill and > reanimate a mere dockapp. -- Joseph Skinner email: [EMAIL PROTECTED] There's no such thing as a wizard who minds his own business - Berengis the Black Court Mage to the Earls Caeline
