Path: chuka.playstation.co.uk!news From: george_bain@playstation.sony.com (George Bain) Newsgroups: scee.yaroze.programming.2d_graphics Subject: Re: ResetGraph(?) Date: 18 Nov 1998 11:08:39 GMT Organization: Sony Computer Entertainment Europe Lines: 27 Distribution: world Message-ID: <72u9rn$olq2@chuka.playstation.co.uk> References: <72fcu3$5bg3@chuka.playstation.co.uk> <364B59EB.347DD52B@scee.sony.co.uk> <72ft10$5bg6@chuka.playstation.co.uk> <364BE9B9.53A631D7@scee.sony.co.uk> <72qf11$dvm4@chuka.playstation.co.uk> <72roir$dvm6@chuka.playstation.co.uk> <365192C6.F844E3AB@writeme.com> NNTP-Posting-Host: mailgate.scee.sony.co.uk Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII X-Newsreader: WinVN 0.99.8 (x86 32bit) Hi there, No, it was because of menu programs that launched example programs such as the ball demo. That's why the ball demo uses ResetGraph(3)....so when you exited the example program back to the menu the screen would't get messed up. George In article , rfredw@argonet.co.uk says... > Oh, and as to the "so why *does* everyone use ResetGraph(3) at the end, >when it ain't documented" question, it's a case of "because the original >(balls) example did". > > Which in turn is because the authors of *that* were used to the pro >libs, and that's what people who are used to the pro libs do, because >they need to unhook from the graphic system without destroying the >loading screen, before chaining in the next process. > > ttfn > Fred