On Mon, Jun 09, 2003 at 02:40:47PM +0200, Moe Wibble wrote:
> > floatws_destroy, IIRC. region_close is not implemented by workspaces.
> Humm, gotta give this some more trying. My first attempts weren't
> successful. (best i could get out of it were some wierd lua errors...)
You must call it with the floatws as an argument. To get this you can use
e.g. lookup_region or region_manager(_) in a query opened in a frame managed
by the workspace (the client windows in that frame will end up in full screen
mode at the moment).
> > region_manage_new(_, {type="WFloatWS"})
> Hmm. That created a new, empty frame with a '?' in the title.
> I couldn't figure out how to put anything into that frame nor
> how to get rid of it (floatws_destroy didn't do it for me).
Just drag windows there from elsewhere, or give the workspace a name
(name="foobar" in the above table with the type or with region_set_name)
and set the target winprop if you want certain windows to always be put
there. With scripts other schemes should be possible as well. The
interrogation mark is shown because the workspace has no name.
> Btw have you ever considered making transients optionally floating on top
> of everything (incl. frames) or on top of the app inside the parent frame?
> Maybe ion can do that already (probably with some tricky lua-script?),
It should be possible to frame a transient with a script, but frame window
switching bindings would stop working as they would apply to the transient
window frame and it would not be possible to move the transient (but I
don't even want that... all apps should just have "minibuffers" for these
features :).
--
Tuomo
