>>>>> "AV" == Andrew Veliath <veliaa_at_rpi.edu> writes:
>>>>> "DJ" == David Johnson <root_at_tiberius.ec.rhno.columbia.edu> writes:
DJ> I was clearing out some of my old saved messages, and came across
DJ> something like, "it won't be too hard to impliment in the next
DJ> version (pre-x.42)" in reply to the request to allow the button 1
DJ> to be the pixmap of the icon already assigned by the style lists.
DJ> This doesn't seem to have been implimented, and I was wondering if
DJ> it had been dropped or forgotten. I remember there was discussion
DJ> about active scaling of the pixmap, so it would fit as a button
DJ> without having to create a new file, and having to tell fvwm about
DJ> two separate styles, one for the icon, and one for the button.
AV> The main problem with this is that anti-aliasing must be performed
AV> (since you are discretely sampling the original). Otherwise there is
AV> always a chance that the reduced pixmap might not look anything like
AV> the original, or at least contain artifacts. There are different
AV> things one can do to try and minimize aliasing effects though.
I don't intend to include anything like this into fvwm. If people
want to put a mini version of the icon as button 1, they can make a
mini pixmap themselves to put there. I don't feel it's necessary to
go through the computational effort to create a mini version on the
fly, as it will serve to only slow down & bloat fvwm, which as you all
know I'm trying hard not to let happen.
The only 'drawback' to them doing it themselves right now is that it
would have to be the same xpm for every window, since the buttons are
global and not per window. I don't know if they ever will be window
specific either.
Chuck
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Wed May 08 1996 - 14:39:36 BST