Re: feature request

Jens Rohler <[email protected]> Tue, 13 Sep 2005 17:53:32 +0200
Newsgroups gmane.compw.window-managers.windowmaker.user
Message-ID <[email protected]>
Hi,

with wdread/wdwrite it is possible to read/write the option StartWorkspace. 
This option controls on which Workspace an application is started. 

You can (temporarily) set the StartWorkspace option for Gimp to 2 if you write 
a script that contains the following commands:
1. Save the old settings for Gimp: 
    OLD=`wdread WMWindowAttributes Gimp`
2. Set the Workspace for Gimp to 2 (2 is the name of the Workspace):
    wdwrite WMWindowAttributes Gimp '{StartWorkspace=2;}'
3. execute gimp
    gimp
4. Then restore the old settings for Gimp with 
     wdwrite WMWindowAttributes Gimp "$OLD"
Execute the last command, when starting gimp is finished (maybe a 
sleep-command between steps 3 and 4).

Jens Rohler

On Friday 09 September 2005 18:00, "Jørn V. Christensen" wrote:
> Hi
>
> Would it be possible to implement a functionality to temporary decide
> which workspace a window pops up. Example:
>
> I am working on a report on workspace 1 and I need to adjust or draw an
> image for the report, so I want to start Gimp. But since it takes some
> some time to start Gimp (yes - a slow machine), so I want to type a command
>    starton 2 gimp
>
> which starts gimp, popping up on workspace 2, while I continue to work
> on workspace 1.
>
> Now, I know I can set that Gimp always has to start on workspace 2 (one
> of my main reasons for using WMaker :) ), but I dont want that with
> Gimp. I just want it to do it this one time.
>
> Is this possible?
>
> Best regards
> Jørn Christensen
> _______________________________________________
> INFO: https://windowmaker.org/lists/listinfo/wm-user
> ARCHIVE: https://windowmaker.org/lists/archive/wm-user/
> FAQ: http://windowmaker.org/faq.html

_______________________________________________
INFO: https://windowmaker.org/lists/listinfo/wm-user
ARCHIVE: https://windowmaker.org/lists/archive/wm-user/
FAQ: http://windowmaker.org/faq.html