Re: winprop.target and nested workspace
Tuomo Valkonen <[email protected]>
| Newsgroups | gmane.comp.window-managers.ion.general |
|---|---|
| Message-ID | <[email protected]> |
On 2008-09-09, Carlos Pita <[email protected]> wrote: > Hi, > > I have saved the following layout into my session: > > groupws1 - frame1 ------groupcw1 -- window1 > |_ groupws2 -- frame2 -- groupcw2 > -- window2 I wouldn't attach a group within a group.. it's asking for a bleeding nose, although in theory the code can handle that. Why not just attach frame2 directly under groupcw1? > But when I restart ion both app1 and app2 end up managed by the tiling > of frame2. In terms of what I see they're siblings at the nested ws > level (groupws2). If I manually attach app1 to frame1 the layout is in > fact rearranged as I desire, so it seems that win.target = frame has a > different semantic than frame:attach(win). When there's no target winprop, Ion starts searching for a place to manage window at, starting from the root window. The target winprop has the semantic of changing that start node (plus a few other things). WGroupCW shouldn't forward prepare_manage calls, though... There could also be some problem with the app2 winprop matching both windows. (Some apps are slow at setting the properties.) -- Tuomo