On Thu, Jan 08, 2004 at 11:41:34AM +0000, Tom Payne wrote: > Adrian Kubala writes: > >If I put the dock on the second Xinerama screen, dockapps which start on > >the first screen don't get put into it. > > I can't test Xinerama features, and have no experience of it so I can't > test anything, but.. The 'auto' dock feature causes the dock to absorb > dockapps started on the same screen as the dock. If there is no dock on the > first screen then the dockapps don't get absorbed anywhere.
The problem is that find_suitable_screen only returns one of the screens on the root window of the client window (the active one, if there's one), but the dock should perhaps try the others as well, if this one doesn't have a dock. In non-xinerama mode this can not be done, of course, and the screen returned by find_suitable_screen is the only possibility. > When the dock starts it doesn't try to manage any existing dockapps. I > doubt that such a behaviour would be desirable anyway: I can see it leading > to all sorts of problems. > > The kludge here is probably to delay startup of your dockapps in your > .xsession. Something like: No. This can't be the problem. The dock decides to manage the dockapps in the add_clientwin_alt hook and this should not be called before Ion has finished reading its configuration files and therefore having loaded the modules. Of course, if you load the dock module later on manually, the dock won't start managing the existing dockapps, as it should not. Also, if you restart Ion, the automatically saved configuration is used. -- Tuomo
