>>So my question is this, i know i can detect going
>>somewhere else with in th cd but is there anything to (for lack of a better
>>word) shut off the qt? or make it inactive?
>
> on endSprite me
> sprite(me.spriteNum).member.movieRate = 0
> end
If I might be so bold as to take a different guess about this (than
Warren or Douglas), I suspect you mean how can you make QuickTime
inactive enough that it gives back the memory that it stole?
Here's a test I just did:
on exitFrame
go the frame
end
on mouseup
if the optiondown then
go frame 11 - the frame
exit
end if
if the shiftdown then
set the movierate of sprite 1 to 1 - the movierate of sprite 1
else
set the movietime of sprite 1 to random(4900)
end if
end
In sprite 1 I have an extremely high data rate movie (3.6 megabytes
per second) that stretches to frame 9. If I option-click I can toggle
between a frame where the movie exists and one where it doesn't. If I
shift-click I toggle the playing of the movie. If I just click, I
randomize the position of the movie.
At the same time I had the freebytes showing in the Watcher window.
In just a few clicks, to randomly jump around the movie, I could see
memory go down by about 25 megabytes. Shift-clicking would not alter
that loss, but a second shift-click (to start the movie playing
again) would free up most of the memory that had been lost. This
seems fair enough, because QuickTime doesn't really mean to keep the
memory, it just has it saved for a moment, in case you need those
recent frames. As soon as you play again it knows that you don't, and
so it releases the memory.
Now, the interesting part is that if I option-click to go to the
frame without the QuickTime sprite, the memory is not freed up. I
think that is the problem that Carol is trying to solve. If I
option-click to get back to the frame with the QuickTime movie, all
the memory is freed up again.
If I'm right that the problem is that QuickTime needs to realize that
it's not going to need those frames, then going to somewhere else
will not convince it.
Ok, this may be a cliff hanger, because I've got a lot of work to do
for the next few hours. You're all welcome to take this further and
suggest solutions. Otherwise, I'll get back onto this later.
--
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
