[SOLVED] Re: FVWM: Causing "firefox" to start in particular desktop page
Dominik, On Tuesday, 2018-02-27 14:36:45 +0100, you wrote: > ... > P.S.: I have this in my config: > > Style Firefox* StartsOnPage 0 1, SkipMapping, MaxWindowSize 99 97 > Style Firefox* fixedpposition The "FixedPPosition" did the trick! Thank you for the quick help :-) > Style Firefox* NoTransientPPosition, NoFuncHint These two were not necessary (at least not in my environment) but they didn't hurt either. Sincerely, Rainer
Re: FVWM:
Michelle, On Tuesday, 2018-02-27 21:44:13 +0200, you wrote: > ... > It does not even work, because the old FvwmTaskbar was AutoHiding after > it lost the focus, I'm not quite sure what exactly you want to achieve, but "FvwmTaskBar" DOES support auto-hiding, if you ask it to do so. Sincerely, Rainer
FVWM: FvwmIconMan problems... gone!
Good day, since I gor -22°C on my BioFarm, I can not do very much as solving IT problems. ;-) Here is the error message I get: [ ~/log/xsession/2018-02-27_210702.log ] FvwmIconMan: Show only focused to: 0 FvwmIconMan: Bad line: *FvwmTaskbarIconsTipstrue FvwmIconMan: What is this: true? FvwmIconMan: Bad line: *FvwmTaskbarIconsTipsOffset 3 2 FvwmIconMan: Unknown option: *FvwmTaskbarIconsTipsOffset FvwmIconMan: Bad line: *FvwmTaskbarIconsSelectButtons flat Green Yellow FvwmIconMan: Unknown option: *FvwmTaskbarIconsSelectButtons IconTips should be "always" and not "true". Maybe the manpage FvwmIconMan should be corrected: *FvwmIconMan: [id] TipsJustification value where value can be leftup, rightdown or center. Specifies the justification (direction) of the tips window relative to its button after the tips window has been placed. Default is leftup which means that if a tip is placed above or below its button, then the left border of the tip and of the button are aligned. If the tip is placed on the left or on the right of its button, leftup aligns the top borders. rightdown and center work like leftup but in different directions. The alignment is adjusted by the TipsOffset option. See next option. ^^ *FvwmIconMan: [id] TipsOffsets placementoffset justoffset ^^^ where placementoffset and justoffset are offsets in pixels for the TipsPlacement and TipsJustification configuration option. Default is 3 2. ...and "SelectButtons" is "SelectButton" ...now I have to get the AutoHide running! Thanks -- Michelle KonzackMiila ITSystems @ TDnet GNU/Linux Developer 00372-54541400
FVWM: FvwmTaskbar autohide strange behaviour
OK guys,
I have this config:
[ ~/.fvwm/Functions/AutoHide.conf ]-
DestroyFunc autohide
AddToFunc autohide
+ I ThisWindow ("$0") Deschedule $[w.id]
+ I ThisWindow ("$0") ThisWindow (Shaded) WindowShade off
+ I TestRc (!Match) All ("$0", !Shaded) autohide_hide $1 $2
DestroyFunc autohide_hide
AddToFunc autohide_hide
+ I Schedule $0 $[w.id] WindowShade $1
+ I Schedule $0 $[w.id] Deschedule $[w.id]
AddToFunc StartFunction
+ I Module FvwmAuto FvwmAutohide -menter enter_handler
DestroyFunc enter_handler
AddToFunc enter_handler
+ I autohide FvwmTaskbarPanel 500 S
and the result is a strange behaviour:
1) The "FvwmTaskbarPanel" is only shown, if I was on "FvwmTaskbar" and
move a little bit up.
From the manpage:
In -menter mode, FvwmAuto raises the window under the
pointer when the pointer enters a window.
In my case, it should act, if I enter "FvwmTaskbar" and then
unhide "FvwmTaskbarPanel". It seems, I have to modify something
because the above 4 functions are universal. I think, in the
case of "FvwmTaskbar" I have to write them explicit for it.
Now it looks like:
[ ~/.fvwm/Functions/AutoHide.conf ]-
DestroyFunc FvwmTaskbarAutohide
AddToFunc FvwmTaskbarAutohide
+ I ThisWindow ("FvwmTaskbarPanel") Deschedule $[w.id]
+ I ThisWindow ("FvwmTaskbarPanel") ThisWindow (Shaded) WindowShade off
+ I TestRc (!Match) All ("FvwmTaskbarPanel", !Shaded)
FvwmTaskbarAutohide_hide 500 S
DestroyFunc FvwmTaskbarAutohide_hide
AddToFunc FvwmTaskbarAutohide_hide
+ I Schedule $0 $[w.id] WindowShade $1500
+ I Schedule $0 $[w.id] Deschedule $[w.id]
AddToFunc StartFunction
+ I Module FvwmAuto FvwmAutohide -menter FvwmTaskbarAutohide
...and it works the same way as before!
2) Sometimes, the "FvwmTaskbarPanel" hide, even the pointer is on focus.
Thanks in advance
--
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400
Re: FVWM: FvwmTaskbar autohide strange behaviour
2018-03-01 5:32 GMT+10:30 Michelle Konzack :
> OK guys,
>
> I have this config:
>
> [ ~/.fvwm/Functions/AutoHide.conf ]-
> DestroyFunc autohide
> AddToFunc autohide
> + I ThisWindow ("$0") Deschedule $[w.id]
> + I ThisWindow ("$0") ThisWindow (Shaded) WindowShade off
> + I TestRc (!Match) All ("$0", !Shaded) autohide_hide $1 $2
>
> DestroyFunc autohide_hide
> AddToFunc autohide_hide
> + I Schedule $0 $[w.id] WindowShade $1
> + I Schedule $0 $[w.id] Deschedule $[w.id]
>
> AddToFunc StartFunction
> + I Module FvwmAuto FvwmAutohide -menter enter_handler
>
> DestroyFunc enter_handler
> AddToFunc enter_handler
> + I autohide FvwmTaskbarPanel 500 S
>
>
> and the result is a strange behaviour:
>
> 1) The "FvwmTaskbarPanel" is only shown, if I was on "FvwmTaskbar" and
>move a little bit up.
>
>From the manpage:
> In -menter mode, FvwmAuto raises the window under the
> pointer when the pointer enters a window.
>
>In my case, it should act, if I enter "FvwmTaskbar" and then
>unhide "FvwmTaskbarPanel". It seems, I have to modify something
>because the above 4 functions are universal. I think, in the
>case of "FvwmTaskbar" I have to write them explicit for it.
>
>Now it looks like:
>
> [ ~/.fvwm/Functions/AutoHide.conf ]-
> DestroyFunc FvwmTaskbarAutohide
> AddToFunc FvwmTaskbarAutohide
> + I ThisWindow ("FvwmTaskbarPanel") Deschedule $[w.id]
> + I ThisWindow ("FvwmTaskbarPanel") ThisWindow (Shaded) WindowShade off
> + I TestRc (!Match) All ("FvwmTaskbarPanel", !Shaded)
> FvwmTaskbarAutohide_hide 500 S
>
> DestroyFunc FvwmTaskbarAutohide_hide
> AddToFunc FvwmTaskbarAutohide_hide
> + I Schedule $0 $[w.id] WindowShade $1500
> + I Schedule $0 $[w.id] Deschedule $[w.id]
>
> AddToFunc StartFunction
> + I Module FvwmAuto FvwmAutohide -menter FvwmTaskbarAutohide
>
>
> ...and it works the same way as before!
Do you mean it's no different from the one where you pass
FvwmTaskbarPanel as a parameter? Because it shouldn't be, unless
something in your command reading pipeline cause parameters to be
expanded when the functions are built rather than at execution. In
that case you could expand them, or try the - command prefix. To see
what actually gets passed around, it might be good to add an Echo at
the start of the function printing all parameters used in that
function.
>
> 2) Sometimes, the "FvwmTaskbarPanel" hide, even the pointer is on focus.
>
I think this might have to do with that on a normal mouse enter you
schedule two commands with the same id, and possibly only deschedule
one, so unless you go in and out twice of the window it would be
shaded anyway. You should remove the + I Schedule $0 $[w.id]
Deschedule $[w.id] from the *_hide functions. And since it will only
consist of a single command then, you could inline Schedule command to
use one function less, and get the logic in one place.
Not, that I'm not entirely sure of how fvwm handles the case where you
schedule multiple commands with the same command id, and then
deschedules that command id, to the above is a best guess at
explaining the behaviour you are seeing.
Regards
//Viktor
