It seems like having the ability to define arguments for user-functions
would greatly increase the flexiblity of ctwm. Let me give an example:
There are many X applications that use child windows spawned from the main
parent winodw, and these windows I have found always appear in the workspace
where you initially started the application the first time they are
instantiated. You can resolve this problem by forcing all windows in the
class of this application to be bound to a certain workspace using the
"Workspace" variable in an "Occupy" definition. However, this means you are
tying the application to 1 particular workspace. What if you want to start
2 or more of the same application in different workspaces? To resolve this
I created 4 functions as follows (I use 4 workspaces named "One" "Two" "Three"
and "Four"):
Function "One_application"
{
f.gotoworkspace "One"
f.exec "application &"
}
Function "Two_application"
{
f.gotoworkspace "Two"
f.exec "application &"
}
etc..
These functions then guarantee that all windows associated with the application
remain in the workspace I intended them to be in.
Problem is this means (in my case) four functions for each application I want
to treat this way, which means a lot of functions! It would be better if I
could define a user-function with arguments such as:
Function "Workspace_application( workspace application )"
{
f.gotoworkspace workspace
f.exec application
}
This then becomes 1 function that could handle all workspaces and applications!
Is this something that would be pretty to implement in ctwm?? I think it would
add great value to an already superior window manager.
Any comments would be appreciated.
-Kevin
This archive was generated by hypermail 2.1.2 : Sat Jun 22 2002 - 06:45:03 CEST