On Fri, Jun 06, 2003 at 06:27:22PM -0400, Paul Pelzl wrote:
> In case you were unaware, it looks like this breaks using the mouse to
> drag a window to a different workspace.
I don't have a *nix computer near me at the moment or until tomorrow,
but IIRC the feature was working just fine. Note that you must first drag
the tab a little to trigger the drag action and only then can you switch
workspaces.
> mplex_move_current_right (and left) are nice to have. I'm still looking
> for a way to automatically "insert workspace before current workspace".
> I can do it manually via query_workspace followed by a number of
> mplex_move_current_left operations, but I don't know how to work out the
> proper number of shifts ahead of time. Any ideas?
There could be some parameter passed to region_do_add_managed, but it might
be best to convert WAttachParams to a Lua table then...
> It seems like it could be useful to be able to obtain more general data
> about a WMPlex; it looks like the geometry information is exported, but
> I don't see any information about the number of frames/workspaces being
> managed or the relative position of the active element in the list.
(mplex|screen|genframe)_current
(mplex|screen|genframe)_managed_list
mplex_nth_managed (I seem to have omitted this from the aliases)
I might add a mplex_managed_count export, but at the moment the following
should do it:
function mplex_managed_count(mplex)
return table.getn(mplex_managed_list(mplex))
end
and to get the position of the current element, you could just search the
list.
I need to update the documentation.
--
Tuomo
