On Wed, Aug 06, 2003 at 09:59:18PM +0300, Mikhael Goikhman wrote:
> On 06 Aug 2003 08:30:27 +0200, Uwe Pross wrote:
> >
> > You may try the following at your box to see the effect:
> >
> > DestroyFunc AutoShadeOn
> > AddToFunc AutoShadeOn I WindowId $0 WindowShade True
> > DestroyFunc AutoShadeOff
> > AddToFunc AutoShadeOff I WindowId $0 WindowShade False
> > Module FvwmAuto 0 -passid "Silent AutoShadeOff" "Silent AutoShadeOn"
> >
> > which should work with 2.4.16.
>
> Actually, the passid options are never really needed in FvwmEvent and
> FvwmAuto. Here is the same code, but shorter and clearer:
>
> DestroyFunc AutoShadeOn
> AddToFunc AutoShadeOn I WindowShade True
> DestroyFunc AutoShadeOff
> AddToFunc AutoShadeOff I WindowShade False
> Module FvwmAuto 0 "Silent AutoShadeOff" "Silent AutoShadeOn"
>
> If you need a condition, you may use ThisWindow instead of "WindowId $0".
Hmm. Interestingly, I received this followup, but not the post of Uwe's
(following up mine) that you were following up to.
I just tried this code, as given, both with and without ThisWindow and
WindowId $0, and it doesn't seem to have the desired result.
With WindowId $0, clicking the new button gives no effect and a logged
error:
[FVWM][execute_function]: <<ERROR>> No such command 'State'
Then each time focus changes from one window to another, the following
errors are logged:
[FVWM][execute_function]: <<ERROR>> No such command 'True'
[FVWM][execute_function]: <<ERROR>> No such command 'False'
With ThisWindow, or with neither ThisWindow nor WindowId $0, the "No
such command 'State'" error still occurs, clicking the new button still
does nothing, and all windows autoshade upon losing focus but never
unshade.
There does not seem to be a 'State' documented anywhere in fvwm-2.4.16.
I can trivially implement a manual per-window WindowShade button, and I
can make all windows automatically Shade, but I don't seem to be able to
make a window automatically unshade, or make a per-window autoshade. Is
this a 2.4.16 limitation?
Experimenting with this has raised another question. The following
ButtonStyle creates a raised button with a narrow raised bar across the
top of the button:
ButtonStyle 3 Vector 5 20x20_at_2 20x30_at_2 80x30_at_0 80x20_at_0 20x20_at_2 -- Raised
The following ButtonStyle *SHOULD*, unless I'm missing something, create
a button like the above with a capital A drawn in the shadow color below
the bar:
ButtonStyle 6 Vector 13 20x20_at_2 20x30_at_2 50x30_at_0 50x40_at_1 90x30_at_2 80x35_at_2 \
80x65_at_2 90x70_at_2 50x40_at_2 50x30_at_1 80x30_at_0 80x20_at_0 20x20_at_2 -- Raised
However, when I load this configuration, this button actually looks the
same as the ButtonStyle 3 button. Can anyone suggest why this would
happen?
(My intention is for Button 3 to be manual-shade and button 6 to be
per-window autoshade, at present. If I ever actually get this
*working*, I'll probably actually swap the two buttons.)
--
.********* Fight Back! It may not be just YOUR life at risk. *********.
: phil stracchino : unix ronin : renaissance man : mystic zen biker geek :
: alaric_at_caerllewys.net : alaric-ruthven_at_earthlink.net : phil_at_latt.net :
: 2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold) :
: Linux Now! ...Because friends don't let friends use Microsoft. :
--
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 Wed Aug 06 2003 - 15:31:30 BST