On 20 Jul 2002 22:10:07 +0200, Dominik Vogt wrote:
>
> On Sat, Jul 20, 2002 at 03:25:12PM +0000, Mikhael Goikhman wrote:
> > On 20 Jul 2002 16:51:35 +0200, Christoph Claus wrote:
> > >
> > > It doesn't work for me... :-(
> >
> > Ok. Several issues here.
> >
> > StaysOnTop just like Layer is one of the not many style options that
> > require RecaptureWindow to be applied. This works in 2.4.x:
> >
> > AddToMenu MenuFvwmWindowOps
> > + "StaysOnTop" StyleAndRecapture $n StaysOnTop
> > + "StaysPut" StyleAndRecapture $n StaysPut
> > + "StaysOnBottom" StyleAndRecapture $n StaysOnBottom
> >
> > AddToFunc StyleAndRecapture
> > + I Style "$0" $1
> > + I All ("$0") RecaptureWindow
> >
> > But this is broken in the current cvs, these style options do not work.
>
> it probably happened by accident, I think it is
> correct that recapturing a window does not modify the window's
> layer. To do this at run time, use the layer command. With the
> same reasoning, changing the "Sticky" and "StartsIconic" styles
> with Recapture should be no-ops too. Remember, I'm still trying
> to obsolete and finally remove the Recapture command.
The question is why "Style X Layer 6" is not applied immediately at the
first place. Then it would be irrelevant whether RecaptureWindow changes
a layer or not.
> > Anyway, if you want only to change layers of one specific window, not
> > all windows with the same name, you may do it without Style:
> >
> > AddToMenu MenuFvwmWindowOps
> > + "StaysOnTop" Layer 0 6
> > + "StaysPut" Layer 0 4
> > + "StaysBottom" Layer 0 2
>
> Or if you want to changle the layers of all windows with the given
> name:
>
> AddToMenu MenuFvwmWindowOps
> + "StaysOnTop" All ($n) Layer 0 6
> + "StaysPut" All ($n) Layer 0 4
> + "StaysBottom" All ($n) Layer 0 2
Just to make it clear that this is not the same as the Style examples that
are at the top of this message, because it only changes the layer of the
windows currently on the screen. If such window is closed and the "same"
one is open, the new one forgets the changed layer unlike Style.
> I recommend not to promote any configs that use the Recapture
> command anymore. As far as I know, it is not recessary to update
> any styles and can be avoided in all other situations too.
I think I knew more cases when Recapture is required, but here are four.
The first two are used in fvwm-themes, the last two is the reason to have
Recapture and RecaptureWindow in menus:
1) + "StaysOnTop" FuncFvwmStyleAndRecapture $n StaysOnTop
2) + "Rearrange icons" All (CurrentDesk Iconic) RecaptureWindow
3) If you have for example, Style "user_at_host" Sticky, and this title
"user_at_host" is set by a shell prompt after a window is captured, you
need Recapture (the only way) to force this style on new terminals.
4) If not for other things Recapture is a more powerful Refresh that may
help in discovering bugs in dynamical Style/BorderStyle/Colorset etc.
A lot of bugs reports in 2.3.x were: X only works after a Recapture.
> Recapture = buggy, inefficient, stupid, visually disturbing... (I
> could continue ranting about it forever).
No problems, but it solves several cases, removing it is not an
immediate option.
Regards,
Mikhael.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sat Jul 20 2002 - 16:36:21 BST