TweetFollow Us on Twitter

Color Animation, Part II
Volume Number:10
Issue Number:5
Column Tag:Getting Started

Related Info: Color Manager

Color Animation, Part II

GWorlds, Bitmaps, PixMaps, and CopyBits - getting the bits flying

By Dave Mark, MacTech Magazine Regular Contributing Author

Note: Source code files accompanying article are located on MacTech CD-ROM or source code disks.

Last month’s column introduced PixMapper, a colorized version of last September’s BitMapper program. BitMapper caused a black and white BitMap to float over a patterned background with absolutely no flicker (Figure 1). BitMapper based its magic on a series of three offscreen BitMaps, BitMaps created in memory but not visible on the screen. The first offscreen contains the foreground image (the left-pointing hand). The second offscreen contains the background image (the grey, framed rectangle). The third offscreen is used to combine the foreground and background before drawing the combined image into the BitMapper window.

Figure 1. Last September’s BitMapper program.

Why does this work? Rather than erasing the old image and repainting it in a new position in the window (in BitMapper’s case, the hand tracks the position of the mouse, sort of a giant cursor), this algorithm repeatedly repaints the entire window, based on the contents of the combining offscreen BitMap. Just as a movie consisting of a series of still frames appears to be a single animated image, the constant repainting of the BitMapper window gives the appearance of an animated image.

Adding Color to the Algorithm

As you’d expect, PixMapper achieves the same affect in color by using PixMaps instead of BitMaps. Just as a BitMap describes a black and white bit pattern, a PixMap describes a color bit pattern. Unfortunately, animation with PixMaps is not quite as simple as its black and white counterpart. Why? A PixMap is just more complex. While a BitMap’s pixels are all either black or white, a PixMap’s pixels can be any one of a number of colors, depending on the depth of the PixMap.

The BitMap data structure is relatively simple:

struct BitMap
 Ptr baseAddr;
 short rowBytes;
 Rect bounds;

Now compare the BitMap to the PixMap data structure:

struct PixMap
 Ptr baseAddr;   /*pointer to pixels*/
 short rowBytes; /*offset to next line*/
 Rect bounds;    /*encloses bitmap*/
 short pmVersion;/*pixMap version number*/
 short packType; /*defines packing format*/
 long packSize;  /*length of pixel data*/
 Fixed hRes;/*horiz. resolution (ppi)*/
 Fixed vRes;/*vert. resolution (ppi)*/
 short pixelType;/*defines pixel type*/
 short pixelSize;/*# bits in pixel*/
 short cmpCount; /*# components in pixel*/
 short cmpSize;  /*# bits per component*/
 long planeBytes;/*offset to next plane*/
 CTabHandle pmTable; /*color map for this pixMap*/
 long pmReserved;/*for future use. MUST BE 0*/

As you can see, the PixMap data structure is far more complicated. In addition, while BitMapper used a GrafPort, PixMapper must use a CGrafPort. As you might suspect, setting up a CGrafPort is more complicated than setting up its black and white counterpart.

The GWorld

Fortunately, rather than forcing you to go through the arduous process of creating and maintaining these far more complex structures, the Toolbox offers a terrific shortcut, namely, the GWorld.

The GWorld is a full-color, offscreen drawing environment. Just as you’d use an offscreen GrafPort and BitMap to prepare a black and white image for blitting to the screen (blitting comes from an old term BLT, which stood for BLock Transfer, meaning to copy a block of memory from one area to another, all at once), you’ll use a GWorld to do the same for a color image. PixMapper demonstrates all this and a little bit more.

Before we get into the code, let’s take a quick look back at PixMapper in action.

Running PixMapper

The PixMapper menu bar features four menus: Apple, File, Edit, and Colors. PixMapper features a single window filling the entire main screen (see GetMainDevice()). PixMapper fills this window with randomly colored squares. Once the window is completely drawn, PixMapper loads a PICT resource, and uses a series of offscreen GWorlds to animate the PICT across the colored background. The speed of your PICT will depend on the speed of your machine and the size of the PICT. The important thing to notice is that the PICT animates smoothly with absolutely no flicker. If there is any hesitation, it is most likely due to the system taking time to do some housekeeping chore. Notice that PixMapper works, even if the PICT is non-rectangular or has a hole in it (see Figure 2).

Figure 2. PixMapper in action.

The PICT starts in the upper-left corner of the window and moves towards the lower right corner. Every time the PICT hits the edge of the window, the PICT will bounce off and continue in the opposite direction.

When you select Redraw from the File menu, PixMapper redraws the window and starts the animation over again.

Go to the Colors menu and play with all the different menu settings. PixMapper lets you play with both the RGB and HSV color models. RGB lets you set a color’s red, green, and blue values. If you uncheck Random Reds, for example, the screen will be redrawn with a red value of 0 (all greens and blues). If Random Reds is checked, the red component of the color is a random value from 0 to 65535.

If you select HSV Colors, you’ll be able to work with hue, saturation, and brightness rather than red, green, and blue. Unlike the RGB menu items, if you uncheck Random Hues, a color’s hues component is set to 65535 instead of 0. Play around with these settings. Do you think you’ll get different results when you choose random RGB versus when you choose random hues?

To learn more about color and the RGB and HSV color models, read “About the Color Manager” in Inside Macintosh, Volume V, THINK Reference or in the upcoming volume Inside Macintosh: Imaging.

The PixMapper Source Code

PixMapper starts off with three critical #includes. <QDOffscreen.h> has all the GWorld defines, <Picker.h> has the definitions needed to work with the RGB and HSV data structures and routines, and <GestaltEqu.h> has the definitions you’ll need to work with Gestalt(). Take a few minutes to look through these three include files.

/* 1 */
#include <QDOffscreen.h>
#include <Picker.h>
#include <GestaltEqu.h>

There are a lot of #defines used in this program. As usual, they’ll all be described as they occur in the code.

/* 2 */
#define kMBARResID 128
#define kSleep   0L
#define kMoveToFront (WindowPtr)-1L
#define kEmptyString "\p"
#define kEmptyTitlekEmptyString
#define kVisible true
#define kNoGoAwayfalse
#define kNilRefCon (long)nil
#define kErrorAlertID128
#define kNilFilterProc  nil

#define kSquareSize16

#define kForegroundPICT 128
#define kIgnored nil
#define kUseMaxDepth 0
#define kNoFlags (GWorldFlags)0

#define mApple   128
#define iAbout   1

#define mFile    129
#define iRedraw  1
#define iQuit    3

#define mColors  131
#define iUseRGB  1
#define iUseHSV  2
#define iRed4
#define iGreen   5
#define iBlue    6
#define iHue4
#define iSaturation5
#define iBrightness6

PixMapper uses a bunch of globals. gDone starts life as false and is set to true when Quit is selected from the File menu. gIsRGB is true when the RGB Colors item is selected from the Colors menu, false when HSV Colors is selected. gRandomReds, gRandomGreens, and gRandomBlues are true when their respective items are selected from the Colors menu. The same holds true for gRandomHue, gRandomSaturation, and gRandomBrightness.

/* 3 */
Boolean gDone;
Boolean gIsRGB = true, gRandomReds = true,
 gRandomGreens = true, gRandomBlues = true;
Boolean gRandomHue = true, gRandomSaturation = true,
 gRandomBrightness = true;

gMainWindow points to the window with all the colors and the animated PICT. gXBump and gYBump specify the number of pixels the PICT moves each new animation cycle. One way to speed up the animation is to raise the bump values, though the code was written do work with single pixel movements. To learn more about the program, try modifying the code to handle any size bump values. You might try using the mouse position to dynamically vary the rate of movement.

/* 4 */
WindowPtr gMainWindow;
short   gXBump = 1, gYBump = 1; // <--Try changing these numbers

We’ll use three GWorlds. gPictWorld holds the PICT image. gSaveWorld holds the background of the window for later restoration. gSaveMixWorld is used to combine the PICT and the background. The three PixMapHandles are handles to the PixMaps tied to their respective GWorld.

/* 5 */
GWorldPtr gPictWorld, gSaveWorld, gSaveMixWorld;
PixMapHandlegPixMapSave, gPixMapSaveMix, gPixMapPict;

gPictWorldRect is the exact size of the PICT and is the bounding rectangle for gPictWorld. gWorldRect is the bounding Rect for the mixing GWorld. The mixing GWorld is one pixel bigger in all directions than the PICT. This was done so that when we save a region the size of gWorldRect from the PixMapper window, we’ll have a one pixel border around the PICT. This way, when the PICT moves one pixel in any direction, we’ll have the right pixels saved for later restoration. You’ll see how this works later in the code. gSavedFloaterRect contains the current position of the PICT in the PixMapper window.

/* 6 */
Rect    gSavedFloaterRect, gPictWorldRect, gWorldRect;

gGlobalHue holds a hue value that we use if HSV Colors is selected from the Colors menu and Random Hues is not selected.

/* 7 */
short   gGlobalHue;

Here are all the function prototypes. Have I mentioned that I always use function prototypes?

/* 8 */
void    ToolboxInit( void );
void    MenuBarInit( void );
Boolean HasGWorlds( void );
void    WindowInit( void );
void    PaintWindow( void );
void    RandomForeColor( void );
void    GWorldInit( void );
GWorldPtr MakeGWorld( Rect *boundsPtr );
void    EventLoop( void );
void    DoEvent( EventRecord *eventPtr );
void    HandleMouseDown( EventRecord *eventPtr );
void    HandleMenuChoice( long menuChoice );
void    HandleAppleChoice( short item );
void    HandleFileChoice( short item );
void    HandleColorsChoice( short item );
void    MainLoop( void );
void    DrawFirstFloater( void );
void    MoveFloater( void );
void    CalcNewFloaterPosition( void );
void    DoError( Str255 errorString );

main() initializes the Toolbox and the menu bar.

/****************** main ***************************/

void  main( void )

See if GWorlds are available on this machine.

/* 9 */
 if ( ! HasGWorlds() )
 DoError("\pDeep GWorlds not supported by this machine!");

If so, create the main window and the three GWorlds.

/* 10 */

Next, plot the initial position of the PICT and enter the main animation loop. The word “floater” refers to the foreground PICT, which appears to float over the background.

/* 11 */
ToolboxInit() and MenuBarInit() are the same as always.

/****************** ToolboxInit *********************/

void  ToolboxInit( void )
 InitGraf( &thePort );
 InitDialogs( NULL );

/****************** MenuBarInit ***********************/

void  MenuBarInit( void )
 Handle menuBar;
 MenuHandle menu;
 menuBar = GetNewMBar( kMBARResID );
 SetMenuBar( menuBar );

 menu = GetMHandle( mApple );
 AddResMenu( menu, 'DRVR' );

HasGWorlds() calls Gestalt() using the selector gestaltQuickdrawFeatures. If Gestalt() returns an error we’ll display an appropriate error message.

/* 12 */
/****************** HasGWorlds *****************/

Boolean HasGWorlds( void )
 long   feature, mask;
 OSErr  err;
 err = Gestalt( gestaltQuickdrawFeatures, &feature );
 if ( err != noErr )
 DoError( "\pError calling Gestalt!" );

Next, we’ll set up a comparison mask so we can look at the appropriate bit in feature. Since gestaltHasDeepGWorlds has a value of 1, we’ll want to look at bit number 1, which is the second bit from the right. We’ll use the << operator to set bit number 1 in mask, leaving mask with a value of 2.

/* 13 */
 mask = 1 << gestaltHasDeepGWorlds;

Finally, we’ll use mask to see if bit number 1 is set in feature. If so, deep GWorlds are available and we’ll return true. Otherwise, we’ll return false. You could also write the following statement as return (feature&mask);

/* 14 */
 if ( feature & mask )
 return true;
 return false;

WindowInit() creates a new color window a little shorter than the main screen. The top of the window starts just below the menu bar. You could also use GetMainDevice() to get the rectangle of the main screen rather than screenBits.bounds.

/* 15 */
/****************** WindowInit ***********************/

void  WindowInit( void )
 Rect   r;
 r = screenBits.bounds; += GetMBarHeight();
 gMainWindow = NewCWindow( nil, &r, kEmptyTitle,
 kVisible, plainDBox, kMoveToFront,
 kNoGoAway, kNilRefCon );

 SetPort( gMainWindow );

Now call PaintWindow() to fill the window with colored rectangles.

/* 16 */

PaintWindow() starts by calculating the number of columns and rows in the PixMapper window.

/* 17 */
/****************** PaintWindow ***********************/

void  PaintWindow( void )
 Rect   r;
 short  row, col, numRows, numCols;
 SetPort( gMainWindow );
 r = gMainWindow->portRect;

Both numCols and numRows are based on kSquareSize. Each square on the window will be kSquareSize pixels on a side. If either numCols or numRows is not evenly divisible by kSquareSize, we’ll add another row or column just so we don’t leave any white space at the edge of the window.

/* 18 */
 numCols = (r.right - r.left) / kSquareSize;
 if ( numCols != numCols/kSquareSize*kSquareSize )
 numRows = (r.bottom - / kSquareSize;
 if ( numRows != numRows/kSquareSize*kSquareSize )

Next, we initialize the random number seed and set gGlobalHue to a random value. We’ll get to gGlobalHue in the next routine.

/* 19 */
 GetDateTime( (unsigned long *)(&randSeed) );
 gGlobalHue = Random();

Next, we’ll step through all the squares, drawing each in the color set by RandomForeColor(). When we’re done, we’ll set the foreground and background colors to their normal values.

/* 20 */
 for ( row=0; row<numRows; row++ )
 for ( col=0; col<numCols; col++ )
 { = row * kSquareSize;
 r.bottom = + kSquareSize;
 r.left = col * kSquareSize;
 r.right = r.left + kSquareSize;
 PaintRect( &r );

 ForeColor( blackColor );
 BackColor( whiteColor );

RandomForeColor() sees which color model is in use.

/* 21 */
/****************** RandomForeColor ***********************/

void  RandomForeColor( void )
 RGBColor color;
 HSVColor hsvColor;

If we’re using RGB colors, we’ll need to specify values for the red, green, and blue fields of the RGBColor. If random reds is turned on, we’ll use a random red, otherwise we’ll set red to 0 (no red at all). The same holds true for green and blue.

/* 22 */
 if ( gIsRGB )
 if ( gRandomReds ) = Random();
 else = 0;
 if ( gRandomGreens ) = Random();
 else = 0;
 if ( gRandomBlues ) = Random();
 else = 0;

Once we set up the color, we’ll make it the new foreground color using RGBForeColor().

/* 23 */
 RGBForeColor( &color );

If we’re using HSV colors, we’ll set values for the hue, saturation, and value fields. Every time you see the value field, think brightness. If gRandomHue is true, we’ll use a random hue, otherwise we’ll use the value stored in gGlobalHue.

/* 24 */
 if ( gRandomHue )
 hsvColor.hue = Random();
 hsvColor.hue = gGlobalHue;

The same holds true for saturation and brightness, except that if random saturation or brightness is turned off, we’ll use a value of 65535 for the saturation or value fields.

/* 25 */
 if ( gRandomSaturation )
 hsvColor.saturation = Random();
 hsvColor.saturation = 65535;
 if ( gRandomBrightness )
 hsvColor.value = Random();
 hsvColor.value = 65535;

Next, we’ll convert the HSV color to an RGB color by calling HSV2RGB() and then pass the RGB color to RGBForeColor().

/* 26 */
 HSV2RGB( &hsvColor, &color );
 RGBForeColor( &color );

GWorldInit() starts by loading the PICT resource.

/* 27 */
/****************** GWorldInit ***********************/

void  GWorldInit( void )
 pic = GetPicture( kForegroundPICT );

 if ( pic == nil )
 DoError( "\pError loading PICT..." );

// Call HNoPurge() if your PICT is purgeable

We’ll normalize the PICT’s frame (offset it to (0,0)).

/* 28 */
 gPictWorldRect = (**pic).picFrame;
 OffsetRect( &gPictWorldRect, - gPictWorldRect.left,
  - );

gWorldRect is set to be 2 pixels taller and 2 pixels wider than the PICT. That gives us room for a one pixel border all the way around.

/* 29 */
 gWorldRect = gPictWorldRect;
 gWorldRect.bottom += 2;
 gWorldRect.right += 2;

Next, we call our own MakeGWorld() routine to build one GWorld the size of the PICT and two the size of gWorldRect, storing the pointers in our three globals.

/* 30 */
 gPictWorld = MakeGWorld( &gPictWorldRect );
 gSaveWorld = MakeGWorld( &gWorldRect );
 gSaveMixWorld = MakeGWorld( &gWorldRect );

When we create a GWorld, a PixMap is created for us. We’ll call GetGWorldPixMap() to store the handle to each PixMap in its respective global.

/* 31 */
 gPixMapPict = GetGWorldPixMap( gPictWorld );
 gPixMapSave = GetGWorldPixMap( gSaveWorld );
 gPixMapSaveMix = GetGWorldPixMap( gSaveMixWorld );

Next, we’ll lock all three PixMaps in memory. Why? Just as you’d lock a handle before you singly dereferenced it to access its pointer, you lock your PixMap before you draw into it. Normally, you’d lock the pixels just before you draw, then unlock the pixels after the call to the drawing routine returns to prevent heap fragmentation. To keep things simple, we’re just going to lock all three PixMaps for the duration of the program.

/* 32 */
 if ( ! LockPixels( gPixMapPict ) )
 DoError( "\pLockPixels failed..." );

 if ( ! LockPixels( gPixMapSave ) )
 DoError( "\pLockPixels failed..." );

 if ( ! LockPixels( gPixMapSaveMix ) )
 DoError( "\pLockPixels failed..." );

Finally, we’ll make the gPictWorld the current GWorld and draw the PICT in it. SetGWorld() makes the specified GWorld the current port and the current gWorld, just as a call to SetPort() might make a window the current port.

/* 33 */
 SetGWorld( gPictWorld, kIgnored );
 DrawPicture( pic, &gPictWorldRect );

MakeGWorld() calls NewGWorld() to create a new GWorld, returning a pointer to the new GWorld. Look up NewGWorld() in Inside Macintosh, Volume VI or in THINK Reference for more detail on the parameters. The first parameter is the address of the GWorldPtr that will eventually point to the new GWorld. The second parameter specifies the pixel depth of the new GWorld. By passing in a value of 0, we’re asking NewGWorld() to use the deepest device that intersects boundsPtr, the third parameter. The fourth and fifth parameters specify a color table and a GDevice, in case you want to roll your own. We’ll pass nil in for each, asking NewGWorld() to take care of these parameters for us. The final parameter lets us set special GWorld flags. We’ll pass in 0, ignoring the flags. You can read about these flags in the description of NewGWorld().

/* 34 */
/*********************************** MakeGWorld */

GWorldPtr MakeGWorld( Rect *boundsPtr )
 QDErr  err;

 err = NewGWorld( &newGWorld, kUseMaxDepth,
 boundsPtr, kIgnored, kIgnored, noNewDevice );

// In the real world, call DisposeGWorld() when you are done with the 
 if ( err != noErr )
 DoError( "\pMy call to NewGWorld died!  Bye..." );
 return( newGWorld );

EventLoop() does its normal thing with one exception. Each time through the loop, the position of the floater is updated via a call to MoveFloater().

/* 35 */
/************************************* EventLoop */

void  EventLoop( void )
 gDone = false;
 while ( gDone == false )
 if ( WaitNextEvent( everyEvent, &event, kSleep, NULL ) )
 DoEvent( &event );

DoEvent() does its normal thing. Notice that we do the absolute minimum when it comes to handling update events. You might want to handle update events in your own code...


/* 36 */

/************************************* DoEvent */

void  DoEvent( EventRecord *eventPtr )
 char theChar;
 switch ( eventPtr->what )
 case mouseDown: 
 HandleMouseDown( eventPtr );
 case keyDown:
 case autoKey:
 theChar = eventPtr->message & charCodeMask;
 if ( (eventPtr->modifiers & cmdKey) != 0 ) 
 HandleMenuChoice( MenuKey( theChar ) );
 case updateEvt:
 BeginUpdate( (WindowPtr)(eventPtr->message) );
 EndUpdate( (WindowPtr)(eventPtr->message) );

The next three routines are the same as ever

/* 37 */
/************************************* HandleMouseDown */

void  HandleMouseDown( EventRecord *eventPtr )
 short  thePart;
 long   menuChoice;
 thePart = FindWindow( eventPtr->where, &window );
 switch ( thePart )
 case inMenuBar:
 menuChoice = MenuSelect( eventPtr->where );
 HandleMenuChoice( menuChoice );
 case inSysWindow : 
 SystemClick( eventPtr, window );

/************************************* HandleMenuChoice */

void  HandleMenuChoice( long menuChoice )
 short  menu;
 short  item;
 if ( menuChoice != 0 )
 menu = HiWord( menuChoice );
 item = LoWord( menuChoice );
 switch ( menu )
 case mApple:
 HandleAppleChoice( item );
 case mFile:
 HandleFileChoice( item );
 case mColors:
 HandleColorsChoice( item );
 HiliteMenu( 0 );

/************************************* HandleAppleChoice */

void  HandleAppleChoice( short item )
 MenuHandle appleMenu;
 Str255 accName;
 short  accNumber;
 switch ( item )
 case iAbout:
 SysBeep( 20 );
 appleMenu = GetMHandle( mApple );
 GetItem( appleMenu, item, accName );
 accNumber = OpenDeskAcc( accName );

When Redraw is selected from the File menu, HandleFileChoice() calls PaintWindow() to redraw the PixMapper window, then calls DrawFirstFloater() to redraw the floater in its initial position.

/* 38 */
/************************************* HandleFileChoice */

void  HandleFileChoice( short item )
 switch ( item )
 case iRedraw:
 case iQuit:
 gDone = true;

HandleColorsChoice() handles all the logic of the Colors menu, changing items and modifying globals as needed. CheckItem() places or removes the check mark from a menu’s item. Once the change is made, we call PaintWindow() and DrawFirstFloater() to restart the process with the modified color scheme.

/* 39 */
/************************************* HandleColorsChoice */

void  HandleColorsChoice( short item )
 MenuHandle menu;
 menu = GetMenu( mColors );
 if ( item == iUseRGB )
 gIsRGB = true;
 SetItem( menu, iRed, "\pRandom Reds" );
 SetItem( menu, iGreen, "\pRandom Greens" );
 SetItem( menu, iBlue, "\pRandom Blues" );
 CheckItem( menu, iUseRGB, true );
 CheckItem( menu, iUseHSV, false );
 CheckItem( menu, iRed, gRandomReds );
 CheckItem( menu, iGreen, gRandomGreens );
 CheckItem( menu, iBlue, gRandomBlues );
 else if ( item == iUseHSV )
 gIsRGB = false;
 SetItem( menu, iHue, "\pRandom Hue" );
 SetItem( menu, iSaturation, "\pRandom Saturation" );
 SetItem( menu, iBrightness, "\pRandom Brightness" );
 CheckItem( menu, iUseRGB, false );
 CheckItem( menu, iUseHSV, true );
 CheckItem( menu, iHue, gRandomHue );
 CheckItem( menu, iSaturation, gRandomSaturation );
 CheckItem( menu, iBrightness, gRandomBrightness );
 else if ( gIsRGB )
 switch ( item )
 case iRed:
 gRandomReds = !gRandomReds;
 CheckItem( menu, iRed, gRandomReds );
 case iGreen:
 gRandomGreens = ! gRandomGreens;
 CheckItem( menu, iGreen, gRandomGreens );
 case iBlue:
 gRandomBlues = ! gRandomBlues;
 CheckItem( menu, iBlue, gRandomBlues );
 switch ( item )
 case iHue:
 gRandomHue = !gRandomHue;
 CheckItem( menu, iHue, gRandomHue );
 case iSaturation:
 gRandomSaturation = ! gRandomSaturation;
 CheckItem( menu, iSaturation, gRandomSaturation );
 case iBrightness:
 gRandomBrightness = ! gRandomBrightness;
 CheckItem( menu, iBrightness, gRandomBrightness );

Here comes the really important stuff. Just as it did in BitMapper, CopyBits() is used to copy a block of pixels from one offscreen to another. Though CopyBits() expects to work with pointers to BitMaps, it can handle either BitMaps or PixMaps. Since the compiler isn’t aware that the called function can handle two different types (BitMap or PixMap), a bit of typecasting is necessary.

/* 40 */
/****************** DrawFirstFloater *********************/

void  DrawFirstFloater( void )

Each call to CopyBits() copies from the first parameter (the source BitMap or PixMap) to the second (destination BitMap or PixMap), using the Rects in the third and fourth parameters. If the rectangles are the same size, no scaling happens, and that’s what we do here. If they are different sizes, CopyBits() stretches or squashes the source to fit the destination. The srcCopy mode tells CopyBits() to replace all the destination bits with the appropriate source bits. The transparent mode, on the other hand, tells the compiler not to copy the white pixels. This comes in handy when we copy a non-rectangular or non-solid image from one GWorld to another. The last parameter to CopyBits() specifies an optional mask parameter which we won’t use. Passing nil tells CopyBits() to ignore this parameter.

The first call to CopyBits() copies the background of the PixMapper window into the gPixMapSave PixMap. We’re saving away the pixels we’re about to obliterate with the PICT, with an extra one pixel border we’ll need when the floater moves in one direction or the other.

/* 41 */
 CopyBits( &(gMainWindow->portBits), 
 (BitMap *)(*gPixMapSave),
 &gWorldRect, &gWorldRect, srcCopy, nil );

Next, we’ll set up a Rect the size of the PICT that is 1 pixel down and 1 pixel to the right of the upper left corner of the window. This is where we’ll plot the PICT.

/* 42 */
 gSavedFloaterRect = gPictWorldRect;
 OffsetRect( &gSavedFloaterRect, 1, 1 );

This draws the PICT in the PixMapper window.

/* 43 */
 CopyBits( (BitMap *)(*gPixMapPict), 
 &gPictWorldRect, &gSavedFloaterRect, transparent, nil );

MoveFloater() calls CalcNewFloaterPosition() to update the values of gXBump and gYBump in case the floater hits the edge of the window.

/* 44 */
/****************** MoveFloater *********************/

void  MoveFloater( void )
 Rect   r;
 RgnHandlenewRgn, savedRgn, oldClip;


This copies the saved pixels to the mixer GWorld.

/* 45 */
 CopyBits( (BitMap *)(*gPixMapSave), 
 (BitMap *)(*gPixMapSaveMix),
 &gWorldRect, &gWorldRect, srcCopy, nil );

Next, we’ll position a Rect the size of the PICT in the mix GWorld using gXBump and gYBump. This Rect is the new position for the floater in the mix GWorld. Then we CopyBits() the floater on top of the saved pixels in the mixing GWorld. Remember, we used transparent mode so we’d only draw the non-background pixels. You would handle this differently if you needed to draw white pixels.

/* 46 */
 r = gPictWorldRect;
 OffsetRect( &r, gXBump + 1, gYBump + 1 );
 CopyBits( (BitMap *)(*gPixMapPict), 
 (BitMap *)(*gPixMapSaveMix),
 &gPictWorldRect, &r, transparent, nil );

Next, we construct a Rect at the floater’s last position in the PixMapper window, then make it one pixel bigger in all directions (the size of the mixing GWorld). We’re use this Rect to copy the contents of the mixing GWorld into the window.

/* 47 */
 r = gSavedFloaterRect;
 InsetRect( &r, -1, -1 );

 CopyBits( (BitMap *)(*gPixMapSaveMix), 
 &gWorldRect, &r, srcCopy, nil );

Next, we update the saved floater position stored in gSavedFloaterRect to reflect the new position.

/* 48 */
 OffsetRect( &gSavedFloaterRect, gXBump, gYBump );

Following that, we’ll create our one pixel bigger Rect again, this time at the floater’s new position, and copy the floater, with a one pixel border, into the mixing GWorld.

/* 49 */
 r = gSavedFloaterRect;
 InsetRect( &r, -1, -1 );
 CopyBits( &(gMainWindow->portBits), 
 (BitMap *)(*gPixMapSaveMix),
 &r, &gWorldRect, srcCopy, nil );

Next, we’ll copy the saved pixels into the appropriate position in the mixing GWorld. The idea here is that we are reconstructing the pixels that should be behind the floater.

/* 50 */
 r = gWorldRect;
 OffsetRect( &r, -gXBump, -gYBump );
 CopyBits( (BitMap *)(*gPixMapSave), 
 (BitMap *)(*gPixMapSaveMix),
 &gWorldRect, &r, srcCopy, nil );

Finally, we’ll copy the reconstructed “behind the floater” pixels from the mix GWorld into the save GWorld. We are now ready to move the floater all over again.

/* 51 */
 CopyBits( (BitMap *)(*gPixMapSaveMix),
 (BitMap *)(*gPixMapSave),
 &gWorldRect, &gWorldRect, srcCopy, nil );

This routine figures out if bumping the floater will move it off the edge of the window in any direction. If so, we change the direction of floater movement so the it moves away from that edge, rather than towards it.

/* 52 */
/*********************************** CalcNewFloaterPosition */

void  CalcNewFloaterPosition( void )
 Rect r;
 r = gSavedFloaterRect;
 OffsetRect( &r, gXBump, gYBump );
 if ( (r.left < gMainWindow->portRect.left) ||
 ( r.right > gMainWindow->portRect.right ) )
 gXBump *= -1;
 if ( ( < gMainWindow-> ||
 ( r.bottom > gMainWindow->portRect.bottom ) )
 gYBump *= -1;

You’ve seen this one before...

/* 53 */
/***************** DoError ********************/

void  DoError( Str255 errorString )
 ParamText( errorString, kEmptyString, 
 kEmptyString, kEmptyString );
 StopAlert( kErrorAlertID, kNilFilterProc );

Till Next Month...

Don’t worry too much about the specifics of the PixMapper algorithm. The important things to understand are how to construct a GWorld, how to use CopyBits() to copy PixMaps between GWorlds and windows, and the basics of working with color. Try your hand at adding some new color schemes to the program. Try going back to Color Mondrian and playing with those colors. Try working with the HSV model, varying only the hue, leaving the saturation and brightness constant. Sometimes RGB does just fine, but sometimes the HSV model really comes in handy.

[If you have a need for even more speed, then you need to think about helping QuickDraw go as fast as it can. There are a number of clues that you can give QuickDraw about what you are doing. CopyBits often gets blamed for poor performance, and it’s true that it can take a good bit of time if you ask it to do something extremely complex (it is capable of a wide range of transforms). If you get to know the call well (by reading Inside Macintosh and the wide variety of sample code available), you can get some blazing speed if you use one of the optimized cases. Many game writers have started out with the assumption that they should avoid CopyBits and write their own blitting routine for performance, only to surprise themselves with the speed CopyBits can offer if used well. Not only can you get terrific performance on 68K Macs, you should try this out on Power Macs where QuickDraw has been rewritten to take advantage of all that PowerPC horsepower. - Ed stb]

I am very interested in animation. I’d love to see your own animation based programs. Once you’ve got something you think is cool, please send the application (no source code, please) to me on Compuserve. My CompuServe address is [70007,2530]. Good luck!

If you can hold out till summer, there’s a new book that you might be interested in. It’s called Ultimate Mac Programming, and (among other things) it will cover both animation and sound. If you are interested in game programming, you might want to check it out. I’ll tell you more about the book as it progresses.

- DM


Community Search:
MacTech Search:

Software Updates via MacUpdate

The best GIF making apps
Animated GIFs have exploded in popularity recently which is likely thanks to a combination of Tumblr, our shorter attention spans, and the simple fact they’re a lot of fun. [Read more] | Read more »
The best remote desktop apps for iOS
We've been sifting through the App Store to find the best ways to do computer tasks on a tablet. That gave us a thought - what if we could just do computer tasks from our tablets? Here's a list of the best remote desktop apps to help you use your... | Read more »
Warhammer 40,000: Freeblade guide - How...
Warhammer 40,000: Freebladejust launched in the App Store and it lets you live your childhood dream of blowing up and slashing a bunch of enemies as a massive, hulking Space Marine. It's not easy being a Space Marine though - and particularly if... | Read more »
Gopogo guide - How to bounce like the be...
Nitrome just launched a new game and, as to be expected, it's a lot of addictive fun. It's called Gopogo, and it challenges you to hoparound a bunch of platforms, avoiding enemies and picking up shiny stuff. It's not easy though - just like the... | Read more »
Sago Mini Superhero (Education)
Sago Mini Superhero 1.0 Device: iOS Universal Category: Education Price: $2.99, Version: 1.0 (iTunes) Description: KAPOW! Jack the rabbit bursts into the sky as the Sago Mini Superhero! Fly with Jack as he lifts impossible weights,... | Read more »
Star Wars: Galaxy of Heroes guide - How...
Star Wars: Galaxy of Heroes is all about collecting heroes, powering them up, and using them together to defeat your foes. It's pretty straightforward stuff for the most part, but increasing your characters' stats can be a bit confusing because it... | Read more »
The best cooking apps (just in time for...
It’s that time of year again, where you’ll be gathering around the dinner table with your family and a huge feast in front of you. [Read more] | Read more »
Square Rave guide - How to grab those te...
Square Rave is an awesome little music-oriented puzzle game that smacks of games like Lumines, but with its own unique sense of gameplay. To help wrap your head around the game, keep the following tips and tricks in mind. [Read more] | Read more »
Snowboard Party 2 (Games)
Snowboard Party 2 1.0 Device: iOS Universal Category: Games Price: $1.99, Version: 1.0 (iTunes) Description: Crowned the best snowboarding game available on the market, Snowboard Party is back to fulfill all your adrenaline needs in... | Read more »
One Button Travel (Games)
One Button Travel 1.0 Device: iOS Universal Category: Games Price: $2.99, Version: 1.0 (iTunes) Description: “To cut a long story short, If you like interactive fiction, just go buy this one.” - “Oozes the polish that... | Read more »

Price Scanner via

Holiday weekend Mac sales roundup: B&H Ph...
B&H Photo continues to have all new Macs on sale for up to $500 off MSRP as part of their Black Friday/Holiday weekend sale. Shipping is free, and B&H charges NY tax only: - 15″ 2.2GHz Retina... Read more
iMobie Releases its Ace iOS Cleaner PhoneClea...
iMobie Inc. has announced the new update of PhoneClean 4, its iOS cleaner designed to reclaim wasted space on iPhone/iPad for use and keep the device fast. Alongside, iMobie hosts a 3-day giveaway of... Read more
U.S. Cellular Offering iPad Pro
U.S. Cellular today announced that it is offering the new iPad Pro with Wi-Fi + Cellular, featuring a 12.9-inch Retina display with 5.6 million pixels — the most ever in an iOS device. U.S. Cellular... Read more
Newegg Canada Unveils Black Friday Deals for...
Newegg Canada is offering more than 1,000 deep discounts to Canadian customers this Black Friday, available now through Cyber Monday, with new deals posted throughout the week. “Black Friday is... Read more
Black Friday: Macs on sale for up to $500 off...
BLACK FRIDAY B&H Photo has all new Macs on sale for up to $500 off MSRP as part of their early Black Friday sale including free shipping plus NY sales tax only: - 15″ 2.2GHz Retina MacBook Pro: $... Read more
Black Friday: Up to $125 off iPad Air 2s at B...
BLACK FRIDAY Walmart has the 16GB iPad Air 2 WiFi on sale for $100 off MSRP on their online store. Choose free shipping or free local store pickup (if available): - 16GB iPad Air 2 WiFi: $399, save $... Read more
Black Friday: iPad mini 4s on sale for $100 o...
BLACK FRIDAY Best Buy has iPad mini 4s on sale for $100 off MSRP on their online store for Black Friday. Choose free shipping or free local store pickup (if available): - 16GB iPad mini 4 WiFi: $299.... Read more
Black Friday: Apple Watch for up to $100 off...
BLACK FRIDAY Apple resellers are offering discounts and bundles with the purchase of an Apple Watch this Black Friday. Below is a roundup of the deals being offered by authorized Watch resellers:... Read more
Black Friday: Target offers 6th Generation iP...
BLACK FRIDAY Save $40 to $60 on a 6th generation iPod touch at Target with free shipping or free local store pickup (if available). Sale prices for online orders only, in-store prices may vary: -... Read more
Black Friday: Walmart and Target offer iPod n...
BLACK FRIDAY Walmart has the 16GB iPod nano (various colors) on sale for $119.20 on their online store for a limited time. That’s $30 off MSRP. Choose free shipping or free local store pickup (if... Read more

Jobs Board

*Apple* Site Security Manager - Apple (Unite...
# Apple Site Security Manager Job Number: 42975010 Culver City, Califo ia, United States Posted: Oct. 2, 2015 Weekly Hours: 40.00 **Job Summary** The Apple Site Read more
WiSE *Apple* Pay Quality Engineer - Apple (...
# WiSE Apple Pay Quality Engineer Job Number: 44313381 Santa Clara Valley, Califo ia, United States Posted: Nov. 13, 2015 Weekly Hours: 40.00 **Job Summary** Join our Read more
Holiday Retail Associate with *Apple* Knowl...
…and assertive.Someone who can troubleshoot iOS devices (iPhone and iPad) and Apple Mail issues.Someone who can offer solutions.Someone who can work weekends.Someone with Read more
*Apple* Systems Engineer (Mclean, VA and NYC...
Summary:Assist in providing strategic direction and technical leadership within the Apple portfolio, including desktops, laptops, and printing environment. This person Read more
Simply Mac *Apple* Specialist- Service Repa...
Simply Mac is the largest premier retailer of Apple products in the nation. In order to support our growing customer base, we are currently looking for a driven Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.