home *** CD-ROM | disk | FTP | other *** search
- Path: toad.stack.urc.tue.nl!not-for-mail
- From: jaco@stack.urc.tue.nl (Jaco Schoonen)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Too system friendly?
- Date: 4 Apr 1996 00:35:35 +0200
- Organization: MCGV Stack, Eindhoven University of Technology, the Netherlands.
- Distribution: inet
- Message-ID: <4juufn$752@toad.stack.urc.tue.nl>
- References: <4jpq5f$i9g@toad.stack.urc.tue.nl> <jdju3z2r5jf.fsf@hyppynaru.cs.hut.fi>
- NNTP-Posting-Host: toad.stack.urc.tue.nl
- X-Newsreader: TIN [version 1.2 PL2]
-
- Osma Ahvenlampi (oahvenla@hyppynaru.cs.hut.fi) wrote:
- : In article <4jpq5f$i9g@toad.stack.urc.tue.nl> jaco@stack.urc.tue.nl (Jaco Schoonen) writes:
- : >The function to update the screen changes those data nad then use several
- : >WritePixelLine8() calls to put them on screen.
- : >On CyberGraphx-screen everything works as expected, but on non-cybergraphx
- : >the data is set to all zero's!
-
- : Yeah. For some reason I've been unable to understand, the V39/V40
- : graphics.library WritePixelLine8() clears the source array after
- : writing it to the destination. I, too, ran into it when my program
- : worked perfectly on a CyberGraphX machine, but failed on a native
- : machine. As far as I'm concerned, CGFX is right here, and the OS is
- : wrong, but that doesn't help much, does it? Unfortunately the only fix
- : is to do an extra copy cycle to create a temporary array to use as the
- : WritePixelLine8() source.
-
- Thanks to everyone that responded. I hope it get's fixed in the next OS
- release, but until then I'll do an extra copy before the write. It's only a
- small array (for 128 pixels) so it shouldn't take too much time...
-
- --
- Jaco Schoonen
- (jaco@stack.urc.tue.nl)
-