Storing images

Ken Ray kray at sonsothunder.com
Mon Feb 3 15:51:01 EST 2003


Judy,

In a cross-platform world, there aren't resource forks on both sides of the
fence, unfortunately, so we need to make do. Now the inelegant solution is
only true if you want the images *embedded* into the stacks; if you don't,
you can leave them on disk and reference them as many times as you like from
wherever you like.

There is also something which is almost as straightforward, although it
makes a copy of an image rather than referencing it, but you could do this
in a pinch:

  put img x into img y

and then to clear it out (so you don't store the "extra" data), you can do:

  put "" into img y

Nice thing about Rev/MC - lots of different ways to get what you want... :-)

Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/

----- Original Message -----
From: "Judy Perry" <jperryl at ecs.fullerton.edu>
To: <use-revolution at lists.runrev.com>
Sent: Monday, February 03, 2003 1:41 PM
Subject: Re: Storing images


> Wow!  What an inelegant "solution".  Is there some technical reason it has
> to be that way?  Even though it involved the use of the dreaded resource
> fork, the Hypercard way of importing such things as images, sounds and the
> like ONCE and then being able to intuitively (as far as addColor anything
> was ever intuitive) reach out and grab any of these things was nice...
>
> Thanks for the solution, though.. I had been wondering as well.
>
> Judy
>
> On Mon, 3 Feb 2003, Malte Brill wrote:
>
> > Hi Jim,
> >
> > you can import the image once, then create a button on each card as a
> > placeholder for that image and set the buttons icon property to the ID
of
> > the image you have imported.
> > Or you can create a group containing your image and set it´s
> > backgroundBehavior to true.
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>




More information about the use-livecode mailing list