TweetFollow Us on Twitter

Event Programming
Volume Number:8
Issue Number:6
Column Tag:Getting Started

Related Info: Event Manager

Event-Based Programming

How a Mac program communicates with the user.

By Dave Mark, MacTutor Regular Contributing Author

So far, you’ve learned how to call Macintosh Toolbox routines in both C and Pascal. You’ve also learned a bit about resource management, mastering the art of WIND based window creation. You’re now ready to take the next step towards Macintosh guru-dom.

Event-based Programming

Most the programs we’ve created together have one thing in common. Each performs its main function, then sits there waiting for a mouse click using this piece of code:

/* 1 */

while ( ! Button() )
 ;

This chunk of code represents the only mechanism the user has to communicate with the program. In other words, the only way a user can talk to one of our programs is to click the mouse to make the program disappear! This month’s program is going to change all that.

One of the most important parts of the Macintosh Toolbox is the Event Manager. The Event Manager tracks all user actions, translating these actions into a form that’s perfect for your program. Each action is packaged into an event record and each event record is placed on the end of the application’s event queue.

For example, when the user presses the mouse button, a mouseDown event record is created. The record describes the mouseDown in detail, including such information as the location, in screen coordinates, of the mouse when the click occurred, and the time of the event, in ticks (60ths of a second) since system startup. When the user releases the mouse button, a second event, called a mouseUp event is queued.

If the user presses a key, a keyDown event is queued, providing all kinds of information describing the key that was pressed. An autoKey event is queued when a key is held down longer than a pre-specified autoKey threshold.

Though there are lots of different events, this month we’re going to focus on four of them: mouseDown, mouseUp, keyDown, and autoKey. Next month we’ll look at some of the others.

Working With Events

Events are the lifeline between your user and your program. They let your program know what your user is up to. Programming with events requires a whole new way of thinking. Up until this point, our programs have been sequential. Initialize the Toolbox, load a WIND resource, show the window, draw in it, wait for a mouse click, then exit.

Event programming follows a more iterative path. Check out the flowchart in Figure 1. From now on, our programs will look like this. First, we’ll perform our program’s initialization. This includes initializing the Toolbox, loading any needed resources, perhaps even opening a window or two. Once initialized, your program will enter the main event loop.

Figure 1. The main event loop flowchart.

The Main Event Loop

In the main event loop, your program uses a Toolbox function named WaitNextEvent() to retrieve the next event from the event queue. Depending on the type of event retrieved, your program will respond accordingly. A mouseDown might be passed to a routine that handles mouse clicks, for example. A keyDown might be passed to a text handling routine. At some point, some event will signal that the program should exit. Typically, it will be a keyDown with the key sequence Q or a mouseDown with the mouse on the Quit menu item. If If it’s not time to exit the program yet, your program goes back to the top of the event loop and retrieves another event, starting the process all over again.

WaitNextEvent() returns an event in the form of an EventRecord struct:

/* 2 */

struct EventRecord
{
    short what;
    longmessage;
    longwhen;
    Point where;
    short modifiers;
};

The what field tells you what kind of event was returned. As I said before, this month we’ll only look at mouseDown, mouseUp, keyDown, and autoKey events, though there are lots more. Depending on the value of the what field, the message field contains four bytes of descriptive information. when tells you when the event occurred, and where tells you where the mouse was when the event occurred. Finally, the modifiers field tells you the state of the control, option, command and shift modifier keys when the event occurred.

EventMaster

This month’s program, EventMaster, displays four lines, one for each of the events we’ve covered so far. As EventMaster processes an event, it highlights that line. For example, Figure 1 shows EventMaster immediately after it processed a mouseDown event.

Figure 2. EventMaster in action.

EventMaster requires a single resource of type WIND. Create a folder called EventMaster in your Development folder. Next, open ResEdit and create a new resource file named EventMaster.Π.rsrc inside the EventMaster folder. Create a new WIND resource according to the specs shown in Figure 3. Make sure the resource ID is set to 128 and the Close Box checkbox is checked. Select Set ‘WIND’ Characteristics from the WIND menu and set the window title to EventMaster. Quit ResEdit, saving your changes.

Figure 3. The WIND resource specifications.

Running EventMaster

Launch THINK C and create a new project named EventMaster.Π in the EventMaster folder. Add MacTraps to the project. Select New from the File menu and type this source code in the window that appears:

/* 3 */

#include <Values.h>

#define kBaseResID 128
#define kMoveToFront (WindowPtr)-1L
#define kSleep   MAXLONG

#define kRowHeight 14
#define kFontSize9

#define kMouseDown 1
#define kMouseUp 2
#define kKeyDown 3
#define kAutoKey 4

/*************/
/*  Globals  */
/*************/

Boolean gDone;
short   gLastEvent = 0;

/***************/
/*  Functions  */
/***************/

void  ToolBoxInit( void );
void  WindowInit( void );
void  EventLoop( void );
void  DoEvent( EventRecord *eventPtr );
void  HandleMouseDown( EventRecord *eventPtr );
void  DrawContents( void );
void  SelectEvent( short eventType );
void  DrawFrame( short eventType );

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

void  main( void )
{
 ToolBoxInit();
 WindowInit();
 
 EventLoop();
}

/*********************************** ToolBoxInit */

void  ToolBoxInit( void )
{
 InitGraf( &thePort );
 InitFonts();
 InitWindows();
 InitMenus();
 TEInit();
 InitDialogs( nil );
 InitCursor();
}

/******************************** WindowInit *********/

void  WindowInit( void )
{
 WindowPtrwindow;
 
 window = GetNewWindow( kBaseResID, nil, kMoveToFront );
 
 if ( window == nil )
 {
 SysBeep( 10 );  /*  Couldn’t load the WIND resource!!!  */
 ExitToShell();
 }
 
 SetPort( window );
 TextSize( kFontSize );
 
 ShowWindow( window );
}

/******************************** EventLoop *********/

void  EventLoop( void )
{
 EventRecordevent;
 
 gDone = false;
 while ( gDone == false )
 {
 if ( WaitNextEvent( everyEvent, &event, kSleep, nil ) )
 DoEvent( &event );
 }
}

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

void  DoEvent( EventRecord *eventPtr )
{
 switch ( eventPtr->what )
 {
 case mouseDown:
 SelectEvent( kMouseDown );
 HandleMouseDown( eventPtr );
 break;
 case mouseUp:
 SelectEvent( kMouseUp );
 break;
 case keyDown:
 SelectEvent( kKeyDown );
 break;
 case autoKey:
 SelectEvent( kAutoKey );
 break;
 case updateEvt:
 BeginUpdate( (WindowPtr)eventPtr->message );
 DrawContents();
 EndUpdate( (WindowPtr)eventPtr->message );
 }
}

/******************************** HandleMouseDown *********/

void  HandleMouseDown( EventRecord *eventPtr )
{
 WindowPtrwindow;
 short  thePart;
 
 thePart = FindWindow( eventPtr->where, &window );
 
 if ( thePart == inGoAway )
 gDone = true;
}

/******************************** DrawContents *********/

void  DrawContents( void )
{
 short  i;
 WindowPtrwindow;
 
 window = FrontWindow();
 
 for ( i=1; i<=3; i++ )
 {
 MoveTo( 0, (kRowHeight * i) - 1 );
 LineTo( window->portRect.right,
 (kRowHeight * i) - 1 );
 }
 
 MoveTo( 4, 9 );
 DrawString( “\pmouseDown” );
 
 MoveTo( 4, 9 + kRowHeight );
 DrawString( “\pmouseUp” );
 
 MoveTo( 4, 9 + kRowHeight*2 );
 DrawString( “\pkeyDown” );
 
 MoveTo( 4, 9 + kRowHeight*3 );
 DrawString( “\pautoKey” );
 
 if ( gLastEvent != 0 )
 DrawFrame( gLastEvent );
}

/************************************* SelectEvent ********/

void  SelectEvent( short eventType )
{
 Rect   r;
 WindowPtrwindow;
 
 window = FrontWindow();
 r = window->portRect;
 
 if ( gLastEvent != 0 )
 {
 ForeColor( whiteColor );
 DrawFrame( gLastEvent );
 ForeColor( blackColor );
 }
 
 DrawFrame( eventType );
 
 gLastEvent = eventType;
}

/************************************* DrawFrame *********/

void  DrawFrame( short eventType )
{
 Rect   r;
 WindowPtrwindow;
 
 window = FrontWindow();
 r = window->portRect;
 
 r.top = kRowHeight * (eventType - 1);
 r.bottom = r.top + kRowHeight - 1;
 
 FrameRect( &r );
}

Once the source code is typed in, save the file as EventMaster.c. Select Add (not Add...) from the Source menu to add EventMaster.c to the project. Select Run from the Project menu to run EventMaster.

When the EventMaster appears, click the mouse in the window. The mouseDown line will highlight. When you let go of the mouse button, the mouseUp line will highlight. Try this a few times, till you can play the entire drum solo to “Wipeout” on your mouse.

Next, hit a key or two on your keyboard (try any key except one of the modifier keys control, option, shift or command). The keyDown line will highlight. Now press the key and hold it down for a while. After a brief delay, the autoKey line will highlight.

Once you’re done playing, click the mouse in the EventMaster window’s close box to exit the program.

Walking Through the EventMaster Source Code

EventMaster starts off by including the file <Values.h>, where the largest long, MAXLONG, is defined.

/* 4 */

#include <Values.h>

Next, a series of constants are defined. Some you know, some you don’t. The new ones will be explained as they are used in the code.

/* 5 */

#define kBaseResID 128
#define kMoveToFront (WindowPtr)-1L
#define kSleep   MAXLONG

#define kRowHeight 14
#define kFontSize9

#define kMouseDown 1
#define kMouseUp 2
#define kKeyDown 3
#define kAutoKey 4

The global gDone starts off with a value of false. When the mouse is clicked in the window’s close box, gDone will be set to true and the program will exit. gLastEvent keeps track of the last event that occurred, taking on a value of either kMouseDown, kMouseUp, kKeyDown, or kAutoKey. We do this so we can erase the old highlighting (if any) before we draw the new highlighting.

/* 6 */

Boolean gDone;
short   gLastEvent = 0;

As usual, our program includes a function prototype for all our functions.

/* 7 */

/***************/
/*  Functions  */
/***************/

void  ToolBoxInit( void );
void  WindowInit( void );
void  EventLoop( void );
void  DoEvent( EventRecord *eventPtr );
void  HandleMouseDown( EventRecord *eventPtr );
void  DrawContents( void );
void  SelectEvent( short eventType );
void  DrawFrame( short eventType );

main() starts by initializing the Toolbox and loading the WIND resource to build the EventMaster window.

/* 8 */

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

void  main( void )
{
 ToolBoxInit();
 WindowInit();

Next, we enter the main event loop.

/* 9 */

 EventLoop();
}

EventLoop() continuously loops on a call to WaitNextEvent(), waiting for something to set gDone to true. The first parameter to WaitNextEvent() tells you what kind of events you are interested in receiving. The constant everyEvent asks the system to send every event it handles. The second parameter is a pointer to an EventRecord. The third parameter tells the system how friendly your application is to other applications running at the same time. Basically, the number tells the system how many ticks you are willing to sleep while some other application gets some processing time. A high number is friendly. A low number makes you a processor hog. The last parameter specifies a home-base region for the mouse. If the mouse moves outside this region, the system will generate a special event, known as a mouse-moved event. Since we won’t be handling mouse-moved events, we’ll pass nil as this last parameter.

/* 10 */

/******************************** EventLoop *********/

void  EventLoop( void )
{
 EventRecordevent;
 
 gDone = false;
 while ( gDone == false )
 {

WaitNextEvent() will return true if it successfully retrieved an event from the event queue. In that case, we’ll process the event by passing it to DoEvent().

/* 11 */


 if ( WaitNextEvent( everyEvent, &event, kSleep, nil ) )
 DoEvent( &event );
 }
}

WaitNextEvent() is described in detail in Inside Macintosh, Volume VI, on page 5-29. If you get a chance, read chapter 5, which describes the Event Manager in detail. You might also want to refer to Chapter 4 in the 2nd edition of the Macintosh C Programming Primer.

DoEvent() switches on eventPtr->what, sending the appropriate constant to the routine SelectEvent(), which highlights the appropriate line in the EventMaster window.

/* 12 */

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

void  DoEvent( EventRecord *eventPtr )
{
 switch ( eventPtr->what )
 {

In the case of a mouseDown, we also pass the event on to our HandleMouseDown() routine, which will check for a mouseDown in the window’s close box.

/* 13 */

 case mouseDown:
 SelectEvent( kMouseDown );
 HandleMouseDown( eventPtr );
 break;
 case mouseUp:
 SelectEvent( kMouseUp );
 break;
 case keyDown:
 SelectEvent( kKeyDown );
 break;
 case autoKey:
 SelectEvent( kAutoKey );
 break;

OK, I know I promised we were only going to handle four event types this month, but I couldn’t help but sneak this one in here. An update event is generated by the system when the contents of your window need to be redrawn. We’ll get to updateEvt next month. In the meantime, if you want to force this code to execute, try triggering your screen dimmer, or cover the EventMaster window with another window and then uncover it..

/* 14 */

 case updateEvt:
 BeginUpdate( (WindowPtr)eventPtr->message );
 DrawContents();
 EndUpdate( (WindowPtr)eventPtr->message );
 }
}

HandleMouseDown() calls FindWindow() to find out in which window, and in which part of the window, the mouse was clicked.

/* 15 */

/******************************** HandleMouseDown *********/

void  HandleMouseDown( EventRecord *eventPtr )
{
 WindowPtrwindow;
 short  thePart;
 
 thePart = FindWindow( eventPtr->where, &window );

If the mouse was clicked in the close box (also known as the goaway box), set gDone to true.

/* 16 */

 if ( thePart == inGoAway )
 gDone = true;
}

DrawContents() draws the contents of the EventMaster window. Notice that the highlighting routine DrawFrame() is only called if a previous event has been handled.

/* 17 */

/******************************** DrawContents *********/

void  DrawContents( void )
{
 short  i;
 WindowPtrwindow;
 
 window = FrontWindow();
 
 for ( i=1; i<=3; i++ )
 {
 MoveTo( 0, (kRowHeight * i) - 1 );
 LineTo( window->portRect.right,
 (kRowHeight * i) - 1 );
 }
 
 MoveTo( 4, 9 );
 DrawString( “\pmouseDown” );
 
 MoveTo( 4, 9 + kRowHeight );
 DrawString( “\pmouseUp” );
 
 MoveTo( 4, 9 + kRowHeight*2 );
 DrawString( “\pkeyDown” );
 
 MoveTo( 4, 9 + kRowHeight*3 );
 DrawString( “\pautoKey” );
 
 if ( gLastEvent != 0 )
 DrawFrame( gLastEvent );
}

SelectEvent() erases the old highlighting (if it existed) and then draws the new highlighting.

/* 18 */

/************************************* SelectEvent  */

void  SelectEvent( short eventType )
{
 Rect   r;
 WindowPtrwindow;
 
 window = FrontWindow();
 r = window->portRect;
 
 if ( gLastEvent != 0 )
 {
 ForeColor( whiteColor );
 DrawFrame( gLastEvent );
 ForeColor( blackColor );
 }
 
 DrawFrame( eventType );
 
 gLastEvent = eventType;
}

DrawFrame() draws the highlighting rectangle.

/* 19 */

/************************************* DrawFrame *********/

void  DrawFrame( short eventType )
{
 Rect   r;
 WindowPtrwindow;
 
 window = FrontWindow();
 r = window->portRect;
 
 r.top = kRowHeight * (eventType - 1);
 r.bottom = r.top + kRowHeight - 1;
 
 FrameRect( &r );
}

Some Homework

To understand more about events, read the Event Manager chapters in Inside Macintosh, Volumes I and VI. You may have noticed that EventMaster left a lot of room on the right side of each of its event lines. Use this space as a scratch pad, drawing information culled from the EventRecord each time you process an event.

As an example, try writing out the contents of the when and where fields. How about pulling the character and key codes out of the message field of a keyDown event. Think of EventMaster as an event playground. Play. Learn.

Next Month and Pascal

Next month, we’ll dig into some events designed specifically for the Window Manager: update and activate events. Till then, I’ll leave you with a Pascal translation of the EventMaster program. See you next month...

program EventMaster;
 const
  kBaseResID = 128;
  kSleep = $FFFFFFFF;
  kRowHeight = 14;
  kFontSize = 9;
  kMouseDown = 1;
  kMouseUp = 2;
  kKeyDown = 3;
  kAutoKey = 4;

 var
  gDone: BOOLEAN;
  gLastEvent: INTEGER;

{----------------> DrawFrame<--}

 procedure DrawFrame (eventType: INTEGER);
  var
   r: Rect;
   window: WindowPtr;
 begin
  window := FrontWindow;
  r := window^.portRect;

  r.top := kRowHeight * (eventType - 1);
  r.bottom := r.top + kRowHeight - 1;

  FrameRect(r);
 end;

{----------------> SelectEvent<--}

 procedure SelectEvent (eventType: INTEGER);
  var
   r: Rect;
   window: WindowPtr;
 begin
  window := FrontWindow;
  r := window^.portRect;

  if gLastEvent <> 0 then
  begin
   ForeColor(whiteColor);
   DrawFrame(gLastEvent);
   ForeColor(blackColor);
  end;

  DrawFrame(eventType);

  gLastEvent := eventType;
 end;

{----------------> DrawContents  <--}

 procedure DrawContents;
  var
   i: INTEGER;
   window: WindowPtr;
 begin
  window := FrontWindow;

  for i := 1 to 3 do
  begin
   MoveTo(0, (kRowHeight * i) - 1);
   LineTo(window^.portRect.right, (kRowHeight * i) - 1);
  end;

  MoveTo(4, 9);
  DrawString(‘mouseDown’);

  MoveTo(4, 9 + kRowHeight);
  DrawString(‘mouseUp’);

  MoveTo(4, 9 + kRowHeight * 2);
  DrawString(‘keyDown’);

  MoveTo(4, 9 + kRowHeight * 3);
  DrawString(‘autoKey’);

  if gLastEvent <> 0 then
   DrawFrame(gLastEvent);
 end;

{----------------> HandleMouseDown <--}

 procedure HandleMouseDown (event: EventRecord);
  var
   window: WindowPtr;
   thePart: INTEGER;
 begin
  thePart := FindWindow(event.where, window);

  if thePart = inGoAway then
   gDone := true;
 end;

{----------------> DoEvent<--}

 procedure DoEvent (event: EventRecord);
 begin
  case event.what of
   mouseDown: 
   begin
    SelectEvent(kMouseDown);
    HandleMouseDown(event);
   end;
   mouseUp: 
    SelectEvent(kMouseUp);
   keyDown: 
    SelectEvent(kKeyDown);
   autoKey: 
    SelectEvent(kAutoKey);
   updateEvt: 
   begin
    BeginUpdate(WindowPtr(event.message));
    DrawContents;
    EndUpdate(WindowPtr(event.message));
   end;
  end;
 end;

{----------------> EventLoop<--}

 procedure EventLoop;
  var
   event: EventRecord;
 begin
  gDone := FALSE;

  while gDone = FALSE do
  begin
   if WaitNextEvent(everyEvent, event, kSleep, nil) then
    DoEvent(event);
  end;
 end;

{----------------> WindowInit <--}

 procedure WindowInit;
  var
   window: WindowPtr;
 begin
  window := GetNewWindow(kBaseResID, nil, WindowPtr(-1));

  if window = nil then
  begin
   SysBeep(10);
   ExitToShell;
  end;

  SetPort(window);
  TextSize(kFontSize);

  ShowWindow(window);
 end;

{----------------> EventMaster<--}

begin
 gLastEvent := 0;

 WindowInit;

 EventLoop;
end.

 
AAPL
$566.75
Apple Inc.
-3.81
GOOG
$602.00
Google Inc.
-7.46
MSFT
$29.00
Microsoft Corpora
-0.11
MacNews Search:
Community Search:
view counter

view counter
view counter
view counter
view counter
view counter
view counter
view counter
view counter

Slingshot Racing Review
Slingshot Racing Review By Carter Dotson on May 24th, 2012 Our Rating: :: SWING ME AROUNDUniversal App - Designed for iPhone and iPad Slingshot Racing is a racing game where players must race around the courses by grappling and swinging around the slippery courses.   | Read more »
Go to the Cannes Film Festival with The...
For the movie industry the Cannes Film Festival is one of the most important events in which to preview films and watch the stars. The 65th annual festival is happening in France right now, but if you weren’t able to secure an invite or make the journey, hope is not lost. Film buffs and star gazers can keep tabs on the festival with The Hoolywood... | Read more »
David Haye’s Knockout Review
David Haye’s Knockout Review By Jennifer Allen on May 24th, 2012 Our Rating: :: PUNCHING FUNUniversal App - Designed for iPhone and iPad A simple yet satisfying cartoon-style boxing game.   | Read more »
WhosHere Updates, Adds Video Chat for Fr...
A mobile social discovery app, WhosHere, updated yesterday, adding free video chat to the universal iOS build. The app allows users connect with an new emphasis on keeping random hook-ups safe(ish). The developers say “the biggest problem in meeting people online today [is] knowing that the person you are speaking to is exactly who they say they... | Read more »
Are You Smarter Than A 5th Grader? &...
Are You Smarter Than A 5th Grader? & Friends Free Review By Jennifer Allen on May 24th, 2012 Our Rating: :: LACKINGUniversal App - Designed for iPhone and iPad An underwhelming use of a great franchise.   | Read more »
Fruit Ninja Gets New Update With Powerup...
Fruit Ninja is about to get its biggest update yet to celebrate its second anniversary on Thursday, May 24th. The key new element in the game appears to be that players will now be able to earn an in-game currency, called starfruit, that can be used to buy new powerups from new characters Gutsu and Truffles, introduced in the new trailer produced... | Read more »
Fotor – CameraBag Review
Fotor – CameraBag Review By Jennifer Allen on May 23rd, 2012 Our Rating: :: PLENTIFULiPhone App - Designed for the iPhone, compatible with the iPad A photography app that wants to be able to do everything that could ever be asked of it.   | Read more »
playGO AP1 is the Next Generation of Aud...
With all of Apple’s relatively recent success in the smartphone and tablet market, we can forget sometimes that what kicked off their modern dominance was a device that simply played music. BICOM, Inc. has been recognizing how important music is to the company with their playGo series of iOS receiver systems. The newest model, the playGo AP1, is... | Read more »
Monkey Pong Review
Monkey Pong Review By Angela LaFollette on May 23rd, 2012 Our Rating: :: BALL BUSTING ACTIONiPhone App - Designed for the iPhone, compatible with the iPad Help the hungry monkey reach all the fruit by bouncing a ball in this family-friendly arcade game.   | Read more »
Heroes & Generals Enters Closed Beta
Creators of Hitman, Roto-Moto, has launched a closed beta of their game, Heroes & Generals. The game is a massively multiplayer first-person shooter involving online fighting between the Axis and Allied forces in Europe. | Read more »
All contents are Copyright 1984-2010 by Xplain Corporation. All rights reserved. Theme designed by Icreon.