Re: FVWM: Windows appearing where they were invoked?

2006-04-17 Thread seventh guardian
On 4/17/06, Mikhael Goikhman [EMAIL PROTECTED] wrote: On 17 Apr 2006 00:45:10 +0100, seventh guardian wrote: There's a minor itch though: it takes me back to the page where it started. Even so, it's better than before! Then you didn't use my implementation of StartHere with SkipMapping:

Re: FVWM: Windows appearing where they were invoked?

2006-04-17 Thread Viktor Griph
On Mon, 17 Apr 2006, seventh guardian wrote: On 4/17/06, Mikhael Goikhman [EMAIL PROTECTED] wrote: On 17 Apr 2006 00:45:10 +0100, seventh guardian wrote: There's a minor itch though: it takes me back to the page where it started. Even so, it's better than before! Then you didn't use my

Re: FVWM: Windows appearing where they were invoked?

2006-04-17 Thread Thomas Adam
--- Elliot Sowadsky [EMAIL PROTECTED] wrote: Could the style instead be removed by the add_window event? No, but you can always make it listen on the add_window event, if you so wished. -- Thomas Adam ___ 24 FIFA

Re: FVWM: Windows appearing where they were invoked?

2006-04-16 Thread Viktor Griph
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

Re: FVWM: Windows appearing where they were invoked?

2006-04-16 Thread Mikhael Goikhman
On 16 Apr 2006 11:54:17 +0100, seventh guardian wrote: It doesn't seem to work.. It appears that the current page vars get updated before they are read. Here's what I have: DestroyFunc StartHere AddToFunc StartHere + I Style $1 StartsOnPage $[desk.n] $[page.nx] $[page.ny] + I Exec exec

Re: FVWM: Windows appearing where they were invoked?

2006-04-16 Thread seventh guardian
On 4/17/06, seventh guardian [EMAIL PROTECTED] wrote: On 4/16/06, Mikhael Goikhman [EMAIL PROTECTED] wrote: On 16 Apr 2006 11:54:17 +0100, seventh guardian wrote: It doesn't seem to work.. It appears that the current page vars get updated before they are read. Here's what I have:

Re: FVWM: Windows appearing where they were invoked?

2006-04-16 Thread seventh guardian
On 4/16/06, Mikhael Goikhman [EMAIL PROTECTED] wrote: On 16 Apr 2006 11:54:17 +0100, seventh guardian wrote: It doesn't seem to work.. It appears that the current page vars get updated before they are read. Here's what I have: DestroyFunc StartHere AddToFunc StartHere + I Style $1

Re: FVWM: Windows appearing where they were invoked?

2006-04-16 Thread Mikhael Goikhman
On 17 Apr 2006 00:45:10 +0100, seventh guardian wrote: There's a minor itch though: it takes me back to the page where it started. Even so, it's better than before! Then you didn't use my implementation of StartHere with SkipMapping: DestroyFunc StartHere AddToFunc StartHere +

Re: FVWM: Windows appearing where they were invoked?

2006-04-16 Thread Mikhael Goikhman
On 17 Apr 2006 00:49:29 +0100, seventh guardian wrote: Oh.. and another one: if the app gets executed from a terminal or from another app, it goes to the same page as before.. not good if you have rox-desktop or any other launching app or desklet.. Maybe if I delete the style afterwards :?

FVWM: Windows appearing where they were invoked?

2006-04-15 Thread seventh guardian
Hello to all. I'm using fvwm with a single desktop and 3x3 pages. 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

Re: FVWM: Windows appearing where they were invoked?

2006-04-15 Thread Elliot Sowadsky
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