On Mar 13, 4:53=A0pm, David Fanning <n...@[EMAIL PROTECTED]
> wrote:
> Rick Towler writes:
> > Well, maybe he wants to embed an emblem or logo in a .sav file.
> > Something a bit more "professional" than simply distributing a
separate
> > file. =A0I mean, *anyone* can do that!
>
> > The trick is encoding the image into a function. =A0Like so:
>
>
>http://www.acoustics.wa****ngton.edu/~towler/programs/make_imageFuncti...
>
> > Like the header says, there are I'm sure a load of issues you could
run
> > into. =A0I've used this on a number of smaller images and it works but
I=
> > would expect this to fail with even "medium" resolution images.
=A0Also
> > you'll want to tweak this a bit as I was working with .png files.
>
> Well, I'm sure this has a use somewhere. I'm not sure "professional"
> is the word I would use to describe it, though. "Rube Goldberg
> solution" comes to mind. ;-)
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming (www.dfanning.com)
> Se****e ma de ni thui. ("Perhaps thou speakest truth.")
Hi -
Rick is correct -- I wanted the image to be embedded, not simply
included as a separate file which can be deleted, moved, etc. And the
Rube Goldberg methods seems to be the only option available. So i
have hard-coded the image, similar to what was suggested. But am I
missing something here, in terms of IDL design? Is there some
philosophical reason why one *shouldn't* want to include an embedded
image in a .sav file?
thanks for the input.
dan
|
