On Thu, Feb 12, 2004 at 04:07:00PM +0000, David Given wrote:
> Now, I oculd work out their ID, add lines to my config file, restart, etc. But
> that's a pain; is there an easier way of doing this?
The only two reasons you should have to restart Ion for are upgrading or
unloading modules (we can't do that safely otherwise). Of course, Some
things might be more practical to do by restarting, but up winprops is not.
Just Mod1+F3 include('kludges') to load new kludges.
Also see a recent post on the ML on a script that should help creating the
kludges file... unfortunately xprop doesn't work directly with transients
(see the configuration document for details), and the ML archives for a link
to a patch.
> over the transient, pressing some magic key combination, and having it turn
> into a window? And vice versa, of course. This would be an extremely useful
> thing to be able to do; transients and frames do quite different things, and
> being able to quickly and simply convert a window from one to the other would
> be really nice.
The following (untested) code should detach a transient:
function detach_topmost_transient(cwin)
local l=cwin:managed_list()
local trs=l[table.getn(l)]
if trs then
cwin:manager():attach(trs)
end
end
Put it in *frame_bindings with e.g.
make_current_clientwin_fn(detach_topmost_transient)
There's no way to make a client window manage a transient again, once it
has been detached.
It is sad that so many programs abuse the WM_TRANSIENT_FOR by setting it
for dialogs that are not at all transient in nature (such non-transient
dialogs/toolboxes are pure evil in any case...), and fail to set it for
dialogs that are (e.g. the "what do you want to do with this file" dialog
in Mozilla and Firebird is not marked as transient although it is such
in nature).
--
Tuomo
