On Sat, 15 Apr 2006, Elliot Sowadsky wrote:
< Currently, whenever I start an application, it appears in the current
< page, and not in the page where it was invoked. I guess that is the
< default behaviour of every wm out there, but I wonder if it wouldn't
< be nicer to have the application windows appearing by default in the
< page where they were invoked.
<
< This way you would simply go to page X and start firefox, go to Y and
< open up a terminal, and in Z start amsn. This way you would "populate"
< your work area and then return to the first page where probably
< firefox is already loaded. Currently you either start an app in one
< page and wait for it to load so that you can move to another page, or
< you load them all in the same page and then move them individually.
<
< I believe there is no _real easy_ way to do this, or is it? If there
< isn't, would it be useful or not?
Heres how i do it.
AddToMenu Applications Applications Title
+ app StartOnCurrentDesk app appname
AddToFunc StartOnCurrentDesk
+ I PipeRead `echo Style $1 StartsOnPage $[desk.n] $[page.nx] $[page.ny]`
+ I Exec exec $0
There is no needto PipeRead that Style command.
Some applications support the -xrm flag to specify resources. In that case
it's more efficient to do, for example for xterm:
Exec exec xterm -xrm "*Page:$[desk.n] $[page.nx] $[page.ny]"
/Viktor
