pcooper@eecs.wsu.edu (Phil Cooper - CS495) (04/09/91)
Once again, I turn to the net for unerring wisdom...
I was looking through the RKM Libs&Devs manual the other day and
I came across some (apparently) conflicting information. It has to
do with accessing the graphics primitive calls from intuition. In several
places in the Intuition section, it says that you have full access to ALL
graphics primitive calls:
P. 173:
You are also free to use all of the lower-level Amiga graphics,
animation, and text primitives (from Intuition).
P. 47:
You can use all of the Amiga graphics, animation, and text primitives
in any window...
But, I then turn to the graphics primitives chapter, and I see this:
P: 335:
If you use any of the routines and data structures described in these
sections, your program will essentially take over the entire display.
It will not, therefore, be compatible with the multi-window operating
environment known as Intuition.
So, what gives? Is it only the display routines which can't be used
from within Intuition? If so, why are they described in the graphics
primitives section (when we've been repeatedly told we can use ALL graphics
primitive operations from Intuition). If not, what other routines are off
limits? As you can see, I am confused...
Phil
--
/********************************************************************\
* Real Life: Phillip R. Cooper *
* Email: pcooper@yoda.eecs.wsu.edu *
* Disclaimer: Disclaimer?? I don't need no stinkin' disclaimer!!! *ccplumb@rose.waterloo.edu (Colin Plumb) (04/13/91)
pcooper@eecs.wsu.edu (Phil Cooper - CS495) wrote: > P: 335: > > If you use any of the routines and data structures described in these > sections, your program will essentially take over the entire display. > It will not, therefore, be compatible with the multi-window operating > environment known as Intuition. > So, what gives? That warning only applies to the "Display Routines and Structures section, from page 335 to 353. The off-limits routines are LoadView(), MrgCop() and MakeVPort(). Use the Intuition equivalents RethinkDisplay(), RemakeDisplay() and MakeScreen() instead. The double-buffering techniques described on page 355 doesn't work with intuition, and the dual-playfield stuff requires some care (although it can be done). Onther than that, anything goes, particularly pages 357 onwards. (Although Intuition prepares a RastPort for you when it gives you a window; there's no need to allocate one of your own.) Graphics Primitive: Intuition equivalent: View Off-limits ViewPort Screen RastPort Window -- -Colin