🚀 go-pugleaf

There has been some talk about creating custom copper lists in the past but
I never found a definitive answer to one question I had.  I have already 
created a Copper list that does EVERYTHING I need it to do, (creates a split
screen display with the top display being overscanned and the bottom being
narrow; to section uses 5 bitplanes and the bottom 4; different colormaps;
etc.) now I wanted to know the LEGAL way of using this Copper list.

The way I did it in the past was to steal the gb_LOFCprList vector from the
GfxBase structure and point it to my list.  Now, I know that will break in
future OS versions so I am looking for a better way.  I do not want to go to
the hardware and update the COP1LC and COP1JMP vectors.

Could I do a InitView() call to a NULL View structure and then place my list's
address in the v_LOFCprList vector and then LoadView()?  Would this be an
approved method?  I have heard that the hardware registers will stay the same
in any hardware updates so that I can use the register names in my custom 
Copper list without fear of failure with future OS'.  Is this true?

Thanks for any light you may shed on this topic (again... 8^) ).


- Brett 
 __  __   _  __  _
|  ||  | / ||  || \   Brett S Bourbin
|  ||  ||  ||  ||  |  INTERNET: brett@PIGPEN.UMD.EDU
|  ||  ||  ||  ||  |
 \_||_/ |__||__||__|  Instructional Computing Programs    
     College Park