On Tue, 18 Jul 2000, Sivakatirswami wrote:

> I am posting this again with a proper subject line:
> 
> re space available for undestroyed stack and files downloaded into the cache
> what about movies and sounds?:
> 
> >> Unfortunately this depends on the platform.  Windows 95/98 uses the
> >> regular file system,. . . . Some OSs will notify the user when swap space is
> > getting
> >> low, some don't.  But as a general rule, you should probably just not
> >> be wasteful and then don't worry about it.
> > 
> OK, then I suppose 2 meg of stacks in memory is probably a reasonable limit
> for most machines these days.
> > 
> >>> 2) is the space available for undestroyed stacks in MC's heap space or only
> >>> limited by available RAM?
> > 
> > 
> >>> There's no point in keeping the cached version of the URL around once
> >>> you've opened a stack.  You should "unload" the cached copy
> >>> immediately after opening the stack.
>  
>  What about movies and sounds? If you download a quicktime movie with sound
>  only and no images (one way we like to play sounds because you have control
> over the position of the sound, at least do in Supercard), load it into a
> player object then unload the URL. . .will the movie/sound track still be
> available to play after you unload the URL? i.e is the sound/movie file held
> in memory just like a stack that still exists in the mainstacks?

You can't play sound and movie files from memory or directly from an
HTTP server, nor can you use a player as a container like you can an
image.  You have to save them to files before you can play them, so
this is a non-issue for now.
  Regards,
    Scott

> Hinduism Today
> 
> Sivakatirswami
> Editor's Assistant/Production Manager
> www.HinduismToday.com
> [EMAIL PROTECTED]

********************************************************
Scott Raney  [EMAIL PROTECTED]  http://www.metacard.com
MetaCard: You know, there's an easier way to do that...


Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Reply via email to