Scale ImageSource?
Terry Judd
tsj at unimelb.edu.au
Fri Jan 8 07:25:35 EST 2010
On 8/01/10 6:02 PM, "Scott Rossi" <scott at tactilemedia.com> wrote:
> Recently, Jacque Landman Gay wrote:
>
>>> As Jacque said, an interesting idea Terry. In fact, the imageSource caching
>>> "feature" could actually work to my benefit since the thumbnails could all
>>> be exported to a single temp image without fear of updating the other
>>> imageSource references. Using one fileName would be a bit less messy than
>>> using 40 or so separate exports I would have to deal with (40 thumbnails).
>>
>> Let us know if it works. I have a hunch that Rev will only read the
>> first iteration of the image and all the subsequent imagesource
>> references to the same file will look like the first one. But I'm not
>> sure, so I'm curious. And if it does work, we all have a new trick.
>
> Oops, you're probably right. If I get a chance to try it I'll report back.
Yep - I reckon they will all be the same as well which is why I suggested
using the tempname function to provide a unique file path, writing the image
to it, setting the imagesource and then deleting the temporary file. I might
have confused things unnecessarily by mentioning the caching issue, which on
reflection seems not to be relevant if you use this method.
Terry...
>
> Regards,
>
> Scott Rossi
> Creative Director
> Tactile Media, UX Design
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
More information about the use-livecode
mailing list