>At 7:50 AM -0700 5/22/2002, Rob Cozens wrote: >>* There is no way of sharing a image among several stacks except by >>keeping the image as an individual file. If, for example, one starts >>using an image library stack and references an image in the library, >>a copy of the image is installed in the referencing stack. > >You can create a blank button and set its icon to the image; in this way >the image can reside in any stack that's loaded into memory. (Whether this >is practical depends on whether you just want to display the image, or >whether you need to fiddle with such as the imageData or mask as well.) > >>* One should never put an image in a group that appears on more than >>one card...rather one should place a button referencing the image by >>icon #. If this is not done, a new copy of the image appears in the >>stack's image library every time a card containing the group is >>created. > >Um? Not sure what you are referring to here as "the stack's image library". >Can you give more details? (I've done just this - an image in a group that >appears on more than one card - without problems.)
I can confirm Rob's observation. In the past I made the mistake of using (grouped) images as navigation controls and ended up with gazillions of copies of the same images in the image library - ugly to say the least. Terry... > >-- >Jeanne A. E. DeVoto ~ [EMAIL PROTECTED] >Runtime Revolution Limited - The Solution for Software Development >http://www.runrev.com/ > > >_______________________________________________ >use-revolution mailing list >[EMAIL PROTECTED] >http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
