> Is this really useful though :)? If you really want something like
> this, it should probably be compilation disabled by default I think,
> since for some it would certainly unnecessarily increase memory
> (personally, I determine what the window contains by looking in the
> window rather than at the icon in the upper-left ;^) )
(the suggestion was mainly for fvwm95)
well if you were to have a pixmap in a button, you would be taking up
memory anyway. Therefore if you were to use a pixmap that is already in
the cache, you would save memory. The same goes for pixmaps in menus,
reused they would save memory. I reckon that all you need to do is to
reduce the pixmap's implementation and not its place in memory(i.e. load
the full pixmap and only reduce it for use); unless of course I'm
missing something about the xpm package and X.
> However, probably a "conservative" way to do it might be to add a
> function to pixmap cache which would, given a pixmap file, return a
> [cached] reduced version.
graeme
--
email: G.McCaffery_at_bham.ac.uk
snail mail: University of Birmingham
School of Electrical &
Electronic Engineering
Birmingham
B15 2TT
--
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 Apr 24 1996 - 02:41:52 BST