home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!charnel!rat!usc!elroy.jpl.nasa.gov!swrinde!gatech!rutgers!cbmvax!cbmehq!cbmfra!lionet
- From: lionet@lionfl.adsp.sub.org (Francois Lionet)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: LoadView(0) and sprites: bug in kickstart?
- Message-ID: <rp+fs*C82@lionfl.adsp.sub.org>
- Date: 7 Jan 93 12:43:07 GMT
- References: <1993Jan4.013803.5167@news.uit.no>
- Reply-To: lionet@lionfl.adsp.sub.org (Francois Lionet)
- Organization: Not an organization
- Lines: 33
- X-Newsreader: Arn V1.00 alpha rel2
-
- In article <1993Jan4.013803.5167@news.uit.no>, Boerge Noest writes:
-
- > Now, I LoadView(0) and thought all was ok until a friend of mine tested it
- > on his 4000 and said 'seriously slim sprite of yours'. He use a superhires
- > pointer and my sprite was displayed in superhires too.
-
- I had exactly the same problem with AMOS. The solution is simple (that's
- why it took me a long time to find!).
-
- Just before taking over the hardware (well, branching your copper list), and
- BEFORE calling LoadView(0), open a simple, lowres screen, using OpenScreen from
- intuition. This will force the lowres screen in front of intuition screen,
- change the resolution of the monitor, and force the sprites back to normal.
- Then performs two WaitTOF, time for Intuition to correctly update the
- sprites.
- Limit the bitmaps to 1 bitplane, and as small as possible to avoid loss of
- memory. But after all, any AA machine have got 2 megs minimum.
-
- Now you can do your LoadView(0) + WaitTOF + WaitTOF as recommended
- by Commodore. It works fine even in the trickyest resolutions like
- DBLPal or DBLNtsc...
-
- Upon quitting you software, just reload the default view and then
- close your small screen.
-
- > Thanks.
- My pleasure.
- --
- "The words of AMOS: proclaim free-will and publish!"
- (Old Testament, AMOS 4.5)
- Francois Lionet
- cbmvax!cbmehq!cbmfra!lionfl!lionet
- lionet@lionfl.adsp.sub.org
-