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.

 

Community Search:
MacTech Search:

Software Updates via MacUpdate

Latest Forum Discussions

See All

Fresh From the Land Down Under – The Tou...
After a two week hiatus, we are back with another episode of The TouchArcade Show. Eli is fresh off his trip to Australia, which according to him is very similar to America but more upside down. Also kangaroos all over. Other topics this week... | Read more »
TouchArcade Game of the Week: ‘Dungeon T...
I’m a little conflicted on this week’s pick. Pretty much everyone knows the legend of Dungeon Raid, the match-3 RPG hybrid that took the world by storm way back in 2011. Everyone at the time was obsessed with it, but for whatever reason the... | Read more »
SwitchArcade Round-Up: Reviews Featuring...
Hello gentle readers, and welcome to the SwitchArcade Round-Up for July 19th, 2024. In today’s article, we finish up the week with the unusual appearance of a review. I’ve spent my time with Hot Lap Racing, and I’m ready to give my verdict. After... | Read more »
Draknek Interview: Alan Hazelden on Thin...
Ever since I played my first release from Draknek & Friends years ago, I knew I wanted to sit down with Alan Hazelden and chat about the team, puzzle games, and much more. | Read more »
The Latest ‘Marvel Snap’ OTA Update Buff...
I don’t know about all of you, my fellow Marvel Snap (Free) players, but these days when I see a balance update I find myself clenching my… teeth and bracing for the impact to my decks. They’ve been pretty spicy of late, after all. How will the... | Read more »
‘Honkai Star Rail’ Version 2.4 “Finest D...
HoYoverse just announced the Honkai Star Rail (Free) version 2.4 “Finest Duel Under the Pristine Blue" update alongside a surprising collaboration. Honkai Star Rail 2.4 follows the 2.3 “Farewell, Penacony" update. Read about that here. | Read more »
‘Vampire Survivors+’ on Apple Arcade Wil...
Earlier this month, Apple revealed that poncle’s excellent Vampire Survivors+ () would be heading to Apple Arcade as a new App Store Great. I reached out to poncle to check in on the DLC for Vampire Survivors+ because only the first two DLCs were... | Read more »
Homerun Clash 2: Legends Derby opens for...
Since launching in 2018, Homerun Clash has performed admirably for HAEGIN, racking up 12 million players all eager to prove they could be the next baseball champions. Well, the title will soon be up for grabs again, as Homerun Clash 2: Legends... | Read more »
‘Neverness to Everness’ Is a Free To Pla...
Perfect World Games and Hotta Studio (Tower of Fantasy) announced a new free to play open world RPG in the form of Neverness to Everness a few days ago (via Gematsu). Neverness to Everness has an urban setting, and the two reveal trailers for it... | Read more »
Meditative Puzzler ‘Ouros’ Coming to iOS...
Ouros is a mediative puzzle game from developer Michael Kamm that launched on PC just a couple of months back, and today it has been revealed that the title is now heading to iOS and Android devices next month. Which is good news I say because this... | Read more »

Price Scanner via MacPrices.net

Amazon is still selling 16-inch MacBook Pros...
Prime Day in July is over, but Amazon is still selling 16-inch Apple MacBook Pros for $500-$600 off MSRP. Shipping is free. These are the lowest prices available this weekend for new 16″ Apple... Read more
Walmart continues to sell clearance 13-inch M...
Walmart continues to offer clearance, but new, Apple 13″ M1 MacBook Airs (8GB RAM, 256GB SSD) online for $699, $300 off original MSRP, in Space Gray, Silver, and Gold colors. These are new MacBooks... Read more
Apple is offering steep discounts, up to $600...
Apple has standard-configuration 16″ M3 Max MacBook Pros available, Certified Refurbished, starting at $2969 and ranging up to $600 off MSRP. Each model features a new outer case, shipping is free,... Read more
Save up to $480 with these 14-inch M3 Pro/M3...
Apple has 14″ M3 Pro and M3 Max MacBook Pros in stock today and available, Certified Refurbished, starting at $1699 and ranging up to $480 off MSRP. Each model features a new outer case, shipping is... Read more
Amazon has clearance 9th-generation WiFi iPad...
Amazon has Apple’s 9th generation 10.2″ WiFi iPads on sale for $80-$100 off MSRP, starting only $249. Their prices are the lowest available for new iPads anywhere: – 10″ 64GB WiFi iPad (Space Gray or... Read more
Apple is offering a $50 discount on 2nd-gener...
Apple has Certified Refurbished White and Midnight HomePods available for $249, Certified Refurbished. That’s $50 off MSRP and the lowest price currently available for a full-size Apple HomePod today... Read more
The latest MacBook Pro sale at Amazon: 16-inc...
Amazon is offering instant discounts on 16″ M3 Pro and 16″ M3 Max MacBook Pros ranging up to $400 off MSRP as part of their early July 4th sale. Shipping is free. These are the lowest prices... Read more
14-inch M3 Pro MacBook Pros with 36GB of RAM...
B&H Photo has 14″ M3 Pro MacBook Pros with 36GB of RAM and 512GB or 1TB SSDs in stock today and on sale for $200 off Apple’s MSRP, each including free 1-2 day shipping: – 14″ M3 Pro MacBook Pro (... Read more
14-inch M3 MacBook Pros with 16GB of RAM on s...
B&H Photo has 14″ M3 MacBook Pros with 16GB of RAM and 512GB or 1TB SSDs in stock today and on sale for $150-$200 off Apple’s MSRP, each including free 1-2 day shipping: – 14″ M3 MacBook Pro (... Read more
Amazon is offering $170-$200 discounts on new...
Amazon is offering a $170-$200 discount on every configuration and color of Apple’s M3-powered 15″ MacBook Airs. Prices start at $1129 for models with 8GB of RAM and 256GB of storage: – 15″ M3... Read more

Jobs Board

*Apple* Systems Engineer - Chenega Corporati...
…LLC,** a **Chenega Professional Services** ' company, is looking for a ** Apple Systems Engineer** to support the Information Technology Operations and Maintenance Read more
Solutions Engineer - *Apple* - SHI (United...
**Job Summary** An Apple Solution Engineer's primary role is tosupport SHI customers in their efforts to select, deploy, and manage Apple operating systems and Read more
*Apple* / Mac Administrator - JAMF Pro - Ame...
Amentum is seeking an ** Apple / Mac Administrator - JAMF Pro** to provide support with the Apple Ecosystem to include hardware and software to join our team and Read more
Operations Associate - *Apple* Blossom Mall...
Operations Associate - Apple Blossom Mall Location:Winchester, VA, United States (https://jobs.jcp.com/jobs/location/191170/winchester-va-united-states) - Apple Read more
Cashier - *Apple* Blossom Mall - JCPenney (...
Cashier - Apple Blossom Mall Location:Winchester, VA, United States (https://jobs.jcp.com/jobs/location/191170/winchester-va-united-states) - Apple Blossom Mall Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.