Previously...
>Has there ever been any discussion about automating the selection of a
>MiniIcon value based on the Icon setting?
>
>What I'm suggesting is something like a global "MiniIconPrefix"
>setting that would calculate a MiniIcon file name by appending the set
>prefix to whatever the Icon value is for a given Style.
>
>This would ease the use of KDE-style icon directories, where there is
>a "/mini" subdirectory within the pixmap directory that contains small
>versions of each image. It also would work for those, like me, who
>keep their mini-icons in the same directory as their pixmaps, but with
>"mini." tagged to the begining of the filename.
>
>Of course, this can also be done by preprocessing the .fvwm2rc (and
>MiniIcon accepts values like "mini/myicon.xpm", interestingly
>enough).
>
>I'm willing to try my (somewhat shakey) hand at a patch, if there's
>enough interest.
But what's wrong with appending the mini subdir into your pixmap path?
I only import my system's /usr/X11R6/include/X11/pixmaps, but I
override builtins by prepending $HOME/pixmaps in my pixmap path. The
mini-* effect is, IMHO, far more annoying and more begs for the patch
you mention, but all the same, I think the general view here is that
there are better ways to approach that "problem" than by hacking fvwm
to do something that a good preprocessor would handle...
--
mikehan_at_best.com
I will not call my teacher `Hot Cakes'
- The collected wisdom of Bart Simpson
--
Visit the official FVWM web page at <URL: http://fvwm.math.uh.edu/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Jan 19 1999 - 12:19:27 GMT