Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!pyramid!amiga!rj
From: rj@amiga.UUCP (Robert J. Mical)
Newsgroups: net.micro.amiga
Subject: Re: Sprite and VSprite info?
Message-ID: <1455@amiga.amiga.UUCP>
Date: Wed, 30-Jul-86 13:31:24 EDT
Article-I.D.: amiga.1455
Posted: Wed Jul 30 13:31:24 1986
Date-Received: Thu, 31-Jul-86 22:01:25 EDT
References: <763@batcomputer.TN.CORNELL.EDU>
Reply-To: rj@amiga.UUCP (Robert J. Mical)
Organization: =RJ Mical=
Lines: 30
Keywords: sprite vsprite

In article <763@batcomputer.TN.CORNELL.EDU> hsgj@batcomputer.TN.CORNELL.EDU (Dan Green) writes:
>   Another problem:  VSprites.  Can't get these things to work at all.
>The RKM is very vague on how one actually goes about defining these.
>We've followed what info was given, which I think consisted of linking
>it into a Gels structure, but there were many ambiguities and the acid
>test -- running the thing -- produced a lot of smoke...

Do you have the 1.1 ROM Kernel Manual?  VSprites are defined pretty well
in there.  Refer to pages 2-113 to 2-129.  If you are programming under
Intuition, ignore the references to the MrgCop() and LoadView() functions,
and instead use the Intuition functions MakeScreen() and RethinkDisplay().

IMPORTANT:  a flaw in the RKManual -- after you initialize your GelsInfo
structure (by calling InitGels()) you *must* set the GelsInfo pointer
in your RastPort to the address of your GelsInfo structure.  This
little detail is omitted from the RKManual.  You most probably want
to use the RastPort of your Screen if you're using Intuition.  Something
like this:
    struct RastPort *rport;
    struct GelsInfo ginfo;

    InitGels(&headsprite, &tailsprite, &ginfo);
    rport = &OpenedScreen->RastPort;
-or-
    rport = address of your own RastPort if you're not using Intuition.

    rport->GelsInfo = &ginfo;


Hope this helps you guys.  Keep the faith.  RJ >:-{)*