Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!oliveb!amiga!dale
From: dale@amiga.UUCP
Newsgroups: comp.sys.amiga
Subject: SetRGB4/LoadRGB4
Message-ID: <1653@amiga.amiga.UUCP>
Date: Mon, 11-May-87 23:43:20 EDT
Article-I.D.: amiga.1653
Posted: Mon May 11 23:43:20 1987
Date-Received: Thu, 14-May-87 03:33:13 EDT
Reply-To: dale@amiga.UUCP (Dale Luck)
Organization: Commodore-Amiga Inc., 16795 Lark Ave. Suite 106, Los Gatos CA 95030
Lines: 14


SetRGB4 and LoadRGB4 affect the existing copper lists directly.
The colors for each ViewPort/Screen are loaded in the few display
lines just before the display appears. So if the processor has stabbed
those locations before the copper reads the instructions then the
colors will change immediately. Your chances of affecting the colors
immediately increase as the screen is located closer to the bottom
of the screen.
While looking at the source, I see a potential/real problem here.
The copperlist is another datastructure that needs arbitration.
So one probably needs to do a LockIBase around your SetRgb/LoadRGB
calls if you are doing it to a screen.
Don't forget your UnlockIBase to
Duck