> > I would propose that the packet look more like:
> >
> > word meaning
> >
> > 0 X Win ID
> > 1 Frame X Win ID
> > 2 Fvwm ID
> > 3 Width
> > 4 Height
> > 5 Depth
> > 6+ File name
> >
> > of course, if the Pixmap ID values are of use, they can be added back in
> > before the file name.
> >
> > A quick check shows that the only module using M_MINI_ICON currently is the
> > FvwmIconMan that comes with Fvwm (I assume the more current version of
> > FvwmIconMan also uses it).
> >
> > Randy
>
> FvwmPager has been modified to use it as well. And I believe the FvwmTaskbar
> module thingy uses them too.
So there is a need for the IDs to stay in. I am currently discussing on the
Perl/Tk mailing list the work that would be needed for having the Photo class
(the class from which images are allocated and created) support a new format
that is just creating a bitmap/pixmap from an ID.
The proposed packet should then be:
word meaning
0 X Win ID
1 Frame X Win ID
2 Fvwm ID
3 Pixmap ID
4 Mask ID
5 Width
6 Height
7 Depth
8+ File name
This would still require that C modules using the M_MINI_ICON packet be
updated, but I think that it is important to have the first three arguments be
consistent with the other packets. Particularly since the Fvwm ID is touted in
several places as a possible database or hash index, due to the guaranteed
uniqueness.
Randy
--
===============================================================================
Randy J. Ray -- U S WEST Technologies IAD/CSS/DPDS Phone: (303)595-2869
Denver, CO rjray_at_uswest.com
"It's not denial. I'm just very selective about the reality I accept." --Calvin
===============================================================================
--
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 Mon Mar 31 1997 - 12:46:38 BST