Re: FVWM: Oddity with Mouse 2 using fvwm 2.6 & 2.7 on Suse Tumbleweed

[mark_at_yahoo]

On 5/10/23 2:39 AM, Klaus Ethgen wrote:
> I cannot say about the other troubles but I do think, the use
> inside of StrartFunction is somewhat wrong.
>
> I have that ImagePath set at the very begin of my .fvwm/config and it
> seems to work well.
>
> Further more, the $HOME does not to be quoted from the documentation.
> However, I do too but with ${HOME}.
Thank you, Klaus. Having ImagePath globally at the beginning of
.fvwm/config instead of in StartFuction makes perfect sense, and I
was sure it was going to solve my problems.

But it did not, nor did changing "$[HOME]" to "$HOME", "${HOME}", or
even explicitly "/home/mark". I keep working on this and have lost
count of how many mysteries there are. They include:

I still can't find a way to examine the value of ImagePath at
runtime. I finally discovered that the output of the "Echo" and other
FVWM Console commands go to $HOME/.xsession-errors, but none of
following gives me what I'm looking for:

    Echo ImagePath
    Echo $ImagePath
    Echo ${ImagePath}
    EchoFuncDefiniton ImagePath
    PrintInfo ImagePath
    PrintInfo ImageCache
    PrintInfo ImageCache verbose 1

Despite the above, I'm absolutely sure my ImagePath is being set
correctly because launcher icons work. My config file has:

    AddToFunc BasicLaunchers
    + I Launcher lockscreen      lkscr lock_brass_72.png \
                                 "xscreensaver-command -lock" \
                                 "-g -816+0"
    + I Launcher firefox         frfox firefox.png     \
                                 firefox            "-g -736+0"
    + I Launcher thunderbird    tbird thunderbird.png thunderbird \
                                "-g -656+0"
    + I Launcher opera          opera opera.png opera \
                                "-g -576+0"

All of those icons work, but they do not (they just show as gray
rectangles) if I comment out:

    # ImagePath 
${HOME}/.local/share/icons/hicolor/48x48:${HOME}/.local/share/icons/hicolor/64x64:${HOME}/.local/share/icons/hicolor/72x72:+

That makes sense because:

    $ fvwm-config --default-imagepath

/usr/share/X11/fvwm2/pixmaps:/usr/share/X11/fvwm2/bitmaps:/usr/share/pixmaps:/usr/share/wallpapers

and:

    $ find $(fvwm-config --default-imagepath | tr : ' ') 
$HOME/.local/share/icons -iname lock_brass_72.png
    find: �/usr/share/X11/fvwm2/bitmaps�: No such file or directory
    /usr/local/home/mark/.local/share/icons/hicolor/72x72/lock_brass_72.png
    $

So FVWM must be picking up my icon path and icons, right? Why do they
work for launchers, but not when iconifying applications?

And more ... if I create an xfce4-terminal, I get:

    $ xprop | fgrep CLASS
    WM_CLASS(STRING) = "xfce4-terminal", "Xfce4-terminal"

FvwmIdent shows the same info. When I iconify it I get a very
nice "terminal" icon, but where is it coming from?

    $ find $(fvwm-config --default-imagepath | tr : ' ') 
$HOME/.local/share/icons -iname \*xfce4-terminal\*
    find: �/usr/share/X11/fvwm2/bitmaps�: No such file or directory
    $

I know this has been too much information but either I'm missing
something obvious or FVWM 2.x still has some bugs after all these
years. Further help from anyone would be greatly appreciated.