Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site vax135.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cjp
From: cjp@vax135.UUCP (Charles Poirier)
Newsgroups: net.micro.amiga
Subject: Q: AmigaBasic access to Amiga features
Message-ID: <1277@vax135.UUCP>
Date: Fri, 31-Jan-86 19:18:23 EST
Article-I.D.: vax135.1277
Posted: Fri Jan 31 19:18:23 1986
Date-Received: Sat, 1-Feb-86 07:44:23 EST
Organization: AT&T Bell Labs, Holmdel, NJ
Lines: 23

I have assorted questions on Microsoft AmigaBasic V1.1.

I remember hearing from some, possibly non-authoritative source, that
with the Amiga one could define a region to be displayed (I don't know
whether to call it a playfield, window, or what), that is bigger than the
screen-area.  And that you could scroll the on-screen region across the
bigger region very simply, as by changing a pointer to the on-screen
origin or some such.

I can't find how to do this in Microsoft AmigaBasic V1.1.  Can it in
fact be done in AmigaBasic?  Can it be done at all?  Is this covered in
some manual set other than what Joe Consumer gets (so far) with V1.1?

Can one coerce the mouse() command to switch its attention from port 1
to port 2 and back?  And: is there a way to read joystick (rather than
mouse) information through AmigaBasic?

Is there a way to have the sound() command use the Attack-Sustain-Decay-
Release envelope?  Is there a way to have one sound channel modulate
another channel, either amplitude or frequency modulation?

	Thanks for any help,
	Charles Poirier