On 07-Jun-00, Julian Aronowitz wrote:
> I can think of two possible work-arounds the programmers can do for
> this problem: 1) have the program temporarily store the image onto a
> disk; and/or, 2) have the program cause a downgrade of resolution of
> the image (from 1200x1200 to 600x400). In either case, less Chip RAM
> will be used at one time, perhaps, preventing a crash.
I don't understand why running out of chip RAM should cause a crash.
Surely on the Amiga you request some memory of a particular type, and if
it isn't available the system returns an error, allowing you to put up a
small requester to warn the user.
I've seen this in so many programs. Why would Voyager be different? Is
it a bug in MUI?
Regards
--
Don Cox
[EMAIL PROTECTED]
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
