Re: Attach client to several workspaces
Matthieu Moy <Matthieu.Moy-wMUr/[email protected]> Tue, 07 Apr 2009 19:03:51 +0200
| Newsgroups | gmane.comp.window-managers.ion.general |
|---|---|
| Message-ID | <[email protected]> |
Oskar Nordquist <[email protected]> writes: > 2009/4/7 Tuomo Valkonen <[email protected]>: >> On 2009-04-07, Oskar Nordquist <[email protected]> wrote: >>> Would it not be easier to just duplicate the client to refer to the same X >>> window? I don't even know if that is possible, but if it is, that's how I'd >>> prefer to do it. >> >> Ummm... I don't know what you really mean. The client always refers to >> the same window it initially created. You can move it around in Ion's >> window management hierarchy (cf. Mod1+A, Mod1+T & Mod1+K A, tab drag), >> also to follow you around. Obviously you can automate this by attaching >> a script to suitable hooks. >> > > I'm not sure how X works, but I'm guessing there is some kind of handle that > an Ion client refers to to draw the window. Would it not be possible to > use this same handle in a new Ion client, which would essentially render the > same window? You cannot have the same application actually running in different frames without application support. At least one problem is that different frames can have different sizes, and the application will draw its content based on the size. With application support, you can do such kind of things (like Emacs "make new frame" for example), but they will still be two distinct frames. What you can do (and what wmii, awesome and other do) is that the resize the window on-the-fly when the workspace changes. Then the application redraws the frame at the new place, with its new size. -- Matthieu