The following are a couple of nuances I've observed. Not
sure if they are bugs or if they are the way things are intended to
be, hence, am posting in the more general USE list rather than the
IMPROVE list:
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.
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):
a) Had trouble
with cryptic error messages (got errors that opened the script error
window for Revolution's source script) when I had the source file
(i.e. a non-standalone stack) very deeply nested. Went away if I
brought it one or two folders closer to root.
b) Likewise,
when I have my distribution executable files deeply nested,
sounds do not play but when I put them at or near desktop there is no
problem.
I suspect both a)
and b) are reflections of the same problem I was having with
gettting backup file errors when trying to save stacks--when I spoke
with Kevin he suggested that perhaps I was at the limit of permissible
filename length for the OS (in this case Mac OS) so that when Rev
tried to save the backup file with the tilde on it, the filename
exceeded the length allowed in the OS.
Has anyone else made
similar observations? What is the limit for filename length?
I certainly can continue to make more folders on my Mac and stuff more
files into these folders, so it doesn't SEEM to be an absolute limit
in the OS. But it certainly DOES seem to be an issue which appears
only when files are deeply nested.
Thanks.
Marian
