> >>>>>>> 2) Then I had a couple of problems which appear to be
>>related to how deeply nested a Rev stack is (both of these
>>observations were on the Mac):
> >>>>>>How long was the pathname to the stack in these cases? (I'm
>not sure what
>the max size of a Mac pathname is offhand, but it seems plausible that this
>stack might have been near the limit....)
Not sure but it was multiple (4-5) folders deep and I tend to use
long folder and filenames. Can maybe try to reconstruct it and get
back to you if you think that would help others.
Marian
>At 6:55 PM -0700 8/20/2001, Marian Petrides, M.D. wrote:
>> 1) I have imported multiple photo images into one card
>>then resized them on the card (by resetting the size of the
>>image in its properties box. Then I saved the stack, closed it
>>anr removed it from memory. Much to my dismay, when I
>>reopened the stack, all the imagese were on the card but in
>>their original (grotesqely large) size. Locking the object's
>>location fixed the problem--apparently locking the object's
>>location also locks its size and this survives a save, close/remove
>>from memory and then reopen.
>
>You pretty much figured this out - images (and players) revert to the size
>of their contents when the card they're on opens. (This is also covered in
>the Troubleshooting section under "Why did an object change size?")
>
>
> > 2) Then I had a couple of problems which appear to be
>>related to how deeply nested a Rev stack is (both of these
>>observations were on the Mac):
>
>How long was the pathname to the stack in these cases? (I'm not sure what
>the max size of a Mac pathname is offhand, but it seems plausible that this
>stack might have been near the limit....)
>
>--
>Jeanne A. E. DeVoto ~ [EMAIL PROTECTED]
>http://www.runrev.com/
>Runtime Revolution Limited - Power to the Developer!
