Discussion:
FVWM: Icon style and Fvwm 2.6.7
B. [simoN] Karhan
2016-12-11 16:36:34 UTC
Permalink
Just a thought, but it may be the change to the /default/config
image path that was introduced into 2.6.7.
previous versions used the "--with-imagepath" value to hardcode
the system path for images. i rectified my personal build
by adding the old imagepath to fvwm/fvwm.c at the point where
it sets it to /default-config/images.

B.
So, I wonder, what changed that made this stuff break..
Can you send your config through, please?
-- Thomas Adam
B. [simoN] Karhan
2016-12-12 01:50:59 UTC
Permalink
ignore previous reponse...
totally off-base...
just had an issue with fvwm finding pixmaps and thus not finding
the icon when iconified (and thus being absent/invisible)...
nothing at all to do with layering...
blah... should not respond to half-read msgs...

B.
Post by B. [simoN] Karhan
Just a thought, but it may be the change to the /default/config
image path that was introduced into 2.6.7.
previous versions used the "--with-imagepath" value to hardcode
the system path for images. i rectified my personal build
by adding the old imagepath to fvwm/fvwm.c at the point where
it sets it to /default-config/images.
B.
So, I wonder, what changed that made this stuff break..
Can you send your config through, please?
-- Thomas Adam
Loading...