Perfect introduction. For multimedia projects which are intense and graphic rich, the amount of resources needed on the user's PC is of concern. Techniques such as switching filenames for images, etc. can be used to keep your "memory overhead" within reasonable limits. But, how do you accurately judge the "project overheads" your software is currently demanding?
In programs like iShell, a key command during evaluation runtime launch from within the editor causes a series of numbers to appear at bottom left of the window. They represent various system use and project demands parameters. Typically the current usage of memory, the high use reached so far and the settings for the project initially. Of most interest is the system heap requirements which can be later be amended for the program by using an .ini file. Okay, enough about a foreign programme, I needed to use it as an example. Can we follow system use and project high/low demands within Revolution? If so how do we get the information dynamically and how do we use it to design our Revolution projects for the least system impact to get the best project? Regards Mark ----- Original Message ----- From: "Geoff Canyon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 20, 2002 3:05 PM Subject: Re: (no subject) snip > > The system heap, on the other hand, is dynamic, and available to other applications. That's why many newer applications -- including Revolution -- allocate memory that way. As others have said, you can change the behaviour of the standalones you build. > > regards, > > Geoff > > _______________________________________________ > use-revolution mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
