TweetFollow Us on Twitter

Control Strip
Volume Number:10
Issue Number:12
Column Tag:New Apple Technology
Related Info: Help Manager

Writing Control Strip Modules

Extend the strip with your own items

By Mike Blackwell, mkb@cs.cmu.edu

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

About the Author

Mike Blackwell - Mike organizes international symposiums, travels around, and figures out how to program things before Apple gets around to documenting them. He’s also been known to do the occasional piece of contract work. Given that chose to go traveling without sending us a bio to fill this space, he’s in no position to dispute our claim that he spends most of his time working for a huge unnamed charitable foundation, handing out large grants to starving software entrepreneurs.

When Apple introduced the PowerBook 500 and Duo 280 series computers, they also released the latest version of System 7. Along with the usual new goodies that accompany a system release this included the Control Strip extension. The Control Strip is a long thin window which floats above all other applications on the desktop, always easily available to the user. When retracted, the Control Strip tucks out of the way in a corner of the desktop. When extended, it presents a row of separate chiclet tiles, each displaying some aspect of system status, such as remaining battery life or the state of file sharing. Some of the tiles allow the user to click on them to quickly change the state of the system through a popup menu or dialog box.

Each of the status tiles in the Control Strip is controlled by a chunk of code called a Control Strip Module (specifically, a resource of type ‘sdev’), which is generally bundled into a corresponding module file. The user can control which modules are available simply by adding or removing the module files from the Control Strip Modules folder in the system folder. At boot time, the Control Strip extension loads and initializes all of the modules found in this folder.

Control strip modules are fairly easy to write. Since the Control Strip extension itself deals with all of the low level interface to the system, the module programmer is freed from the usual minutiae of Macintosh programming such as toolbox initialization, event loops, grafports, and the likes. However, there are still some tricky areas: resource loading, global memory, loading and saving user preferences, and balloon help, for example. In this article we will use MPW to develop a simple module which displays a rudimentary clock, to learn just what makes a Control Strip module tick.

Before we get started, there are a few caveats to keep in mind:

• Space in the Control Strip is a very limited resource, and should not be needlessly cluttered with modules that might be better implemented as applications. The Control Strip should be reserved for information that the user may need convenient access to at any time.

• Since Control Strip modules are always “running,” they should minimize their impact on system performance by consuming as little memory and as few processor cycles as possible.

• Finally, the current release of the Control Strip extension only runs on the PowerBook machines.

If you would like to play with Control Strip on a desktop Mac, you have two options. If you have access to the Control Strip extension (on the System 7.5 installation disk, for example), Rob Mah has produced a nice little patcher program which will modify Control Strip to run on all platforms (by deleting ‘sdev’ resource number -4064 from the extension, which Control Strip uses as a “PowerBook-only” flag). Also, Sigurdur Asgeirsson has written a shareware Control Strip work-alike called Desktop Strip, which will run on all Macs and use most Control Strip modules (some nice ones are provided). These programs are available at finer archive sites everywhere, try:


/* 1 */
ftp://mac.archive.umich.edu/
    mac/system.extensions/cdev/controlstrippatcher2.0.sit.hqx
ftp://mac.archive.umich.edu/
    mac/system.extensions/cdev/desktopstrip1.0.sit.hqx

They are also available on this issue’s code disk and online sites (see p. 2).

Structure of a Module

All code for the module is contained in a code resource of type ‘sdev’ in the module file. Typically a module file has only one ‘sdev’ resource corresponding to one module. If a module file has more than one ‘sdev’ resource, then each is loaded as a separate module, though this gives the user less flexibility in mixing and matching modules. One possible use for multiple modules in one file would be to have different versions of a similar module, only one of which will load depending on the user’s hardware configuration. As we will see shortly, during the initialization process a module can decide for itself if it should stay loaded.

Besides the ‘sdev’ resource, a module file will typically contain a couple of string and picture resources, plus the usual version, icon, and bundle resources to help the user distinguish the file from a generic document. Unless otherwise required, the programmer should number all resources in the range 256 - 32767 to avoid conflicts with other system resources.

In our example module, SimpleCSClock.r is a Rez file which contains all of the resources for the module except for the ‘sdev’ resource, which will be produced by the C compiler. It starts with a version and signature resource, with information to be displayed by the Finder’s Get Info command. The signature (‘cs!C’ in this case) is also used as the file’s creator ID and as a Preferences key, and should be unique. If you are planning to distribute a module widely, its signature should be registered with Apple to prevent conflicts with other applications.

Next is a ‘PICT’ resource which is a picture of a small right-pointing arrow. This will be drawn in the right-hand side of our tile, to indicate to the user that the module provides a popup menu. A ‘MENU’ resource defines that menu, followed by a couple of strings and string lists which will be described later. Finally, a ‘BNDL’, ‘FREF’, and icon family define the icons for the file that the user will see from the Finder.

The header file SimpleCSClock.h defines the various resource and item numbers in a common location for both the Rez and C programs.

Module Initialization and Global Memory

The Control Strip communicates to the module through a single entry point at the beginning of the module’s ‘sdev’ resource. The prototype for this interface is


/* 2 */
pascal long ControlStripModule(long message, long params,
  Rect *statusRect, GrafPtr statusPort);

message signifies which action the Control Strip wishes the module to perform, from which the module can then dispatch the appropriate routines. These actions include module initialization, display management, queries for module features or display size, periodic “tickles,” and a couple of others.

parms is generally used to store a handle to a parameter or global variables needed by the control strip. The statusRect and statusPort variables are used when drawing the control strip tile.

In addition to this message interface, the Control Strip extension also provides the module with a handful of utility toolbox routines which simplify many actions common to most modules (the utility routine names all begin with the letters “SB” - until just before its release, Control Strip was called Status Bar).

Control Strip sends sdevInitModule as the very first message a module receives. This happens as the control strip extension loads modules from the modules folder at boot time. sdevInitModule asks the module to determine if it can run on this particular platform (generally using various calls to Gestalt to query for necessary features), and then initialize its internal state. If the initialization returns a value less than zero to the Control Strip (because it cannot run on this platform or something failed during initialization), then the module is unloaded and not installed in the Control Strip.

In our example, the Initialize() routine is dispatched on receipt of the initialize message (note that params will always be 0 for this message). After checking the machine features, a chunk of memory and a handle to it is allocated to hold all of the global variables that the module will need to maintain its state. These variables are defined in the Globals structure at the beginning of the program. If the initialization proceeds successfully, then the handle to the globals is returned to the Control Strip. On all subsequent message calls to the module the Control Strip will pass this handle in params, so the globals will always be accessible.

The module file will not be open after the first initialize message has been processed, so any resources that the module needs must be loaded from the file during initialization. This is accomplished with toolbox variants of GetResource. Once each resource is loaded in to memory, its handle is stashed in the globals structure, and the resource is detached so it will always be available. One reason why the module file is not left open after initialization is to conserve power on PowerBooks. If the module were to make GetResource calls on a regular basis it would keep the hard disk turned on a lot.

Once the resources are loaded, the Initialize() routine loads and sets any previously saved user’s preferences. This is accomplished using two of the Control Strip’s utility routines. First, SBGetDetachedIndString() is called to get the string item corresponding to the name of our preferences from the recently detached ‘STR#’ resource helpStrings. This name is then passed to SBLoadPreferences() to read the module’s preferences in to the SavedSettings structure. The first field of the preferences structure is checked against 4-byte module signature to make sure these preferences really belong to this module. Finally, the user’s preferences are copied into the globals structure (in this case, there is only one preference: whether to display the time in 12- or 24-hour format).

Maintaining The Display

Once the module has been initialized and loaded, it can go about its business of maintaining its status display in its tile. This is primarily accomplished through two messages from the Control Strip: sdevPeriodicTickle and sdevDrawStatus. For these two messages (and all others as well), the Control Strip passes the handle to our globals structure in params, a pointer to the drawing rectangle in statusRect, and a pointer to the GrafPort in statusPort (which typically you won’t need to access directly).

Note that each time a message is processed after initialization, the first thing the message handler does is save the state of the globals structure handle, and then lock the structure down so it won’t move while the message is being handled. At the completion of the message, the handle’s state is restored. We don’t simply use HLock()/HUnlock(), because modules can be reentrant - it is possible for the Control Strip to call the module’s message handler before a previous message has completed. If this happens and we inadvertently unlock the handle underneath another message’s feet, all hell could break loose. For this same reason, it’s best not to store variables like parameter blocks in the globals structure, since two messages could be trying to modify them at the same time. Allocate these variables on the stack as needed (by declaring them within the scope of the handler routine), or if they must be global, add an in-use flag.

The module performs most of its work in the sdevPeriodicTickle message. This message is called periodically, but there is no guarantee about how often or when it will be called. The sdevPeriodicTickle message gives the module a chance to check whether its status display is out of date, and if so to update it. Since our clock module updates rather slowly (once every minute), there’s no need to check if the time has changed every single time the tickle message is called - once every couple of seconds is adequate and saves wasting cycles needlessly. To accomplish this, we use the nextTick global variable to signal when we need to check if the display is out of date. If the system clock (returned by TickCount()) is less than nextTick, then we return from the message right away without any further processing.

Otherwise, we call UpdateTime(), which checks to see if the time has changed since it was last displayed, and stores the time to be displayed in the globals structure. If the time has changed, the tile rectangle is erased and DrawDisplay() is called to update the display. DrawDisplay(), in turn, converts the current time in to a string, selects the proper font, sets the drawing point within the statusRect, and calls DrawString() to draw the time of day in the module’s tile. DrawDisplay() then draws the small right-pointing arrow picture just to the right of the time string, which indicates that a popup menu is available. Finally, nextTick is set for two seconds from the current time.

After drawing all of the information in the statusRect, the tickle message handler compares the width of what it has just drawn (returned by DrawDisplay()) to the width of what it had drawn the previous time through (and saved in the width field of the globals structure). If the width has changed then the width field is updated, and sdevResizeDisplay bit is set to be returned to the message call. This bit signals to the Control Strip to shrink or grow the module’s tile appropriately so all of the data is visible in the tile.

When the Control Strip is informed that the module’s tile width has changed, it will next send the module an sdevGetDisplayWidth message request. Since the module is maintaining that width anyway, there’s no need to recompute it, and the module simply returns the width field from the globals structure.

The other message which maintains the module’s displays is sdevDrawStatus. This message is sent by the Control Strip when the display needs to be redrawn, such as for a window update or display hilite, and requests the module to draw its display in its tile. In our case, we do this by calling the DrawTime() routine. Since the module will always be displaying the same information it has already displayed, the width will not have changed and the return from DrawDisplay() can be ignored.

User Interaction

Not all modules require input from the user - they may simply display status information - but our clock module allows the user to select the format of the time presentation. The user can select either a 12- or 24-hour display format by clicking on the module’s tile and making a menu selection from the popup menu that appears. The currently selected option is flagged with a bullet (Figure 1).

Figure 1

The module informed the Control Strip that it wanted to process mouse clicks in its tile by setting the sdevWantMouseClicks and sdevDontAutoTrack bits in its reply to an sdevFeatures message. Whenever the Control Strip detects a click in the module’s tile, it does two things: first, it highlights the tile by darkening its background and shifting the display slightly for a 3-D effect, and then it sends the module an sdevMouseClick message. If the sdevDontAutoTrack feature bit had not been set, then the module would not receive the sdevMouseClick message until after the mouse was clicked and then released in the tile, causing the tile to act as a button instead of a menu title.

Our module responds to the sdevMouseClick message by calling its HandleMouseClick() routine. This routine first checks the current display mode, and marks the appropriate selection in the menu with a bullet character (conveniently pre-defined as sdevMenuItemMark). It then displays the popup menu by calling the Control Strip utility routine SBTrackPopupMenu(). Once a menu item has been selected, the appropriate display mode is flagged in the global structure. If the display mode was changed, then the reply to the sdevMouseClick message has the appropriate bits set to inform the Control Strip that the new user preference needs to be saved and that the balloon help message has changed. DrawDisplay() is called with a flag to inhibit actual drawing to compute the width of the new display. Similar to the tickle message, if the width has changed then the global width is updated and the sdevResizeDisplay reply bit is set to inform Control Strip.

User Preferences

The Control Strip provides the module with a very nice mechanism to save its state between shutdown and restart. This state is stored as a ‘pref’ resource in the Control Strip Preferences file in the system Preferences folder.

At some convenient point after a module has requested to save its settings (by setting the sdevNeedToSave bit in the reply to an sdevMouseClick message, for example) it will receive an sdevSaveSettings message. Control Strip typically waits until some other process has powered up the hard disk, or during shutdown time, to send this message. When our module receives this message, it dispatches its SavePreferences() routine. This allocates memory for the SavedSettings structure, which for our module has only two fields: an identifying signature, and the boolean display mode we want to save. The signature is just a safety feature to make sure the module doesn’t get confused later by inadvertently trying to load some other module’s incorrectly stored resource, and we’ll set it to our file creator type. The display mode is just copied from the current mode in the global structure.

Once the settings structure is set up and filled in, the module needs to pick a name for the resource. For convenience, we already predefined this name as an item in the help strings ‘STR#’ resource, so the module calls SBGetDetachedIndString() to retrieve the name. Then the module calls SBSavePreferences() to save the settings structure as a ‘pref’ resource in the preferences file.

On startup these steps are basically performed in reverse to load and set the previously saved settings, as described in the Module Initialization section.

Balloon Help

The Control Strip allows each module to provide simple balloon help to the user. If balloon help is turned on and the module has set the sdevHasCustomHelp feature bit, then the Control Strip will send the module an sdevShowBalloonHelp message when the mouse is sitting in the module’s tile. The module can then call SBShowHelpString() with a descriptive string to be displayed to the user (Figure 2). There is no easy way to provide more detailed help for things like menu items.

Figure 2

If the module changes its mode while handling a tickle or mouse click message, it can set the sdevHelpStateChanged bit in its reply, telling the Control Strip to issue a new sdevShowBalloonHelp message to cause the help string to change.

To give the user more information about the module file, our module has a Finder help string resource (a ‘STR ’ with an ID of -16397). If the user double clicks on the module’s icon from the Finder, the Finder will display a dialog box containing this string, telling the user what the module is and how to use it. We’ve also set a Help Manager resource pointing to this same string. The idea is that balloon help from the Finder will display the string, but this does not currently work because the Finder doesn’t know about ‘sdev’ files so it always displays a generic message. But it only costs a few bytes, and maybe one day the Finder will do the right thing.

Additional Resources

Hopefully, this article has given you enough information to go out and write your own Control Strip modules. The full documentation for the Control Strip API can be found, oddly enough, in Chapter 5 of Apple’s PowerBook 520/520c/540/540c Developer Notes. You can find a copy on any recent Develop Bookmark CD (a very worthwhile addition to your programming library to complement your MacTech magazines). It will also soon be released as a tech note.

The Control Strip header file ControlStrip.h can be found on Apple’s ETO CD #15 and later. If you don’t have access to the “official” version, Rob Mah provides a home grown version along with his patcher. Note that there is a slight inconsistency between Apple’s and Mah’s definitions of the return bits for tickle and feature messages. Apple defines the bit number (for example, sdevHasCustomHelp = 2) while Mah defines the bit position (sdevHasCustomHelp = (1 << 2)). The code in this article uses Apple’s conventions.

Many thanks to Steve Christensen at Apple, Control Strip’s author, for reviewing this article.

SimpleCSClock.h


/* 3 */
#define kSignature 'cs!C'

#define kArrowPictID 256

#define kConfigMenuID256
#define k12HourCmd 1
#define k24HourCmd 2

#define kHelpStringsID    256
#define kPrefNameStr 1
#define kHelp12StringStr  2
#define kHelp24StringStr  3

SimpleCSClock.c


/* 4 */
/* SimpleCSClock - A simple control strip clock module         
 By Mike Blackwell, mkb@cs.cmu.edu 
*/

#include <GestaltEqu.h>
#include <Fonts.h>
#include <Memory.h>
#include <Packages.h>
#include <Resources.h>
#include <Strings.h>
#include <SysEqu.h>
#include <ToolUtils.h>
#include "ControlStrip.h"
#include "SimpleCSClock.h"


// How often to check if the display needs to be updated (in ticks)
#define INTERVAL (2 * 60) // 2 seconds

// Display font information
#define DISPLAY_FONT monaco
#define DISPLAY_FONT_SIZE 9
#define DISPLAY_FONT_FACE 0
#define DISPLAY_MARGIN    3 // Blank space to left and right of text

typedef struct Globals {
 PicHandlearrowPicture;   // Picture to show we have a popup menu
 short  arrowWidth, 
 arrowHeight;    // Size of arrow
 short  fontHeight;// Ascender height of display font
 Handle helpStrings; // Balloon help strings for each state
 MenuHandle configMenu;   // Menu to select display options
 int    width;   // Width of display
 Booleanshow12Hour;// True for 12 hour display
 int    displayTime; // Time that is currently being displayed
 //  (in minutes since midnight)
 unsigned long nextTick;  // When to next update the display
} Globals, *GlobalPtr, **GlobalHandle;


typedef struct SavedSettings {
 OSType signature; // Signature to verify that prefs are for
 //  this module
 Booleanshow12Hour;// True for 12 hour display
} SavedSettings;


/* Prototypes 9/
long    Initialize(void);
void    CleanUp(GlobalHandle globHand);
long    HandleMouseClick(GlobalPtr globPtr, Rect *statusRect);
short   SavePreferences(GlobalPtr globPtr);
Boolean UpdateTime(GlobalPtr globPtr);
intDrawDisplay(GlobalPtr globPtr, Rect *statusRect, 
  Boolean drawit);
Boolean CheckFeatures(void);


pascal long main(long message, 
 long params, 
 Rect *statusRect, 
 GrafPtr statusPort)
{
#pragma unused(statusPort)
 char   savedState;
 GlobalPtrglobPtr;
 long   result;
 int    current_width;
 Str255 helpString;

 if (params > 0) { // If we have globals allocated,
 savedState = HGetState((Handle)params);                       
 //  save the handle state,
 HLock((Handle)params);   //  lock the handle to the globals,
 globPtr = *(GlobalHandle)params;  //  and point to globals directly
 }

 result = 0;// Return zero for unknown messages

 switch (message) {

 case sdevInitModule:// Initialize the module
 result = Initialize();
 break;

 case sdevCloseModule:    // Clean up before being closed
 CleanUp((GlobalHandle)params);
 params = 0L;    // Handle is gone now
 break;

 case sdevFeatures:// Return feature bits
 result = (1 << sdevWantMouseClicks) | \
  (1 << sdevDontAutoTrack)| \
  (1 << sdevHasCustomHelp);
 break;

 case sdevGetDisplayWidth:// Return display width
 result = globPtr->width;
 break;

 case sdevPeriodicTickle: // Periodic tickle when nothing 
 // else is happening
 // Time to update display yet?
 if (TickCount() >= globPtr->nextTick) {                       
 if (UpdateTime(globPtr)) { // Check if time has changed
 EraseRect(statusRect);   // Yep, erase the old
 current_width = DrawDisplay( globPtr, 
   statusRect, 
 true);// And draw the new
 // If the display width changed, let the control strip know
 if (globPtr->width != current_width) {
 globPtr->width = current_width;
 result = (1 << sdevResizeDisplay);
 }
 }
 globPtr->nextTick = TickCount() + INTERVAL;
 }
 break;

 case sdevDrawStatus:// Update the display
 (void)DrawDisplay(globPtr, statusRect, true);
 break;

 case sdevMouseClick:// User clicked on the module's 
 // display area in the status bar
 result = HandleMouseClick(globPtr, statusRect);
 break;

 case sdevSaveSettings:   // Save changed settings
 result = SavePreferences(globPtr);
 break;

 case sdevShowBalloonHelp:// Display custom balloon help
 SBGetDetachedIndString(&helpString, 
 globPtr->helpStrings,
 globPtr->show12Hour ? kHelp12StringStr : kHelp24StringStr);
 SBShowHelpString(statusRect, &helpString);
 break;
 }

 if ((long)params > 0)    // If we have globals allocated,
 HSetState((Handle)params, savedState);//  restore the locked/unlocked 
state

 return(result);
}


Initialize
long Initialize(void)
{
 long   result;
 GlobalPtrglobPtr;
 GlobalHandle  globHand;
 FontInfo fontInfo;
 Str255 prefsResourceName;
 SavedSettings **preferences;

 result = -1;    // Assume failure

 if (!CheckFeatures()) 
 return(result);


 if (! (globHand = 
 (GlobalHandle)NewHandleClear(sizeof(Globals))))
 goto done; // Allocate the globals


 HLock((Handle)globHand); // Lock the globals while using them
 globPtr = *globHand;//  and get a pointer to them

//  Load and detach the ‘up arrow’ picture

 if (! (globPtr->arrowPicture = GetPicture(kArrowPictID))) 
 goto done;


 DetachResource((Handle)globPtr->arrowPicture);

// Compute size of arrow picture

 globPtr->arrowHeight = 
 (**globPtr->arrowPicture).picFrame.bottom
 - (**globPtr->arrowPicture).picFrame.top;
 globPtr->arrowWidth = 
 (**globPtr->arrowPicture).picFrame.right 
 - (**globPtr->arrowPicture).picFrame.left;

// Compute size of display font

 TextFont(DISPLAY_FONT);
 TextSize(DISPLAY_FONT_SIZE);
 TextFace(DISPLAY_FONT_FACE);
 GetFontInfo(&fontInfo);
 globPtr->fontHeight = fontInfo.ascent;

//  Load and detach the configuration menu

 if (! (globPtr->configMenu = GetMenu(kConfigMenuID))) 
 goto done;


 DetachResource((Handle)globPtr->configMenu);

//  Load and detach the help strings

 if (! (globPtr->helpStrings = 
 Get1Resource('STR#', kHelpStringsID))) 
 goto done;


 DetachResource(globPtr->helpStrings);

//  Get the module's saved preferences, if any, and configure the module

 SBGetDetachedIndString(&prefsResourceName, 
  globPtr->helpStrings, kPrefNameStr);
 if (! SBLoadPreferences(&prefsResourceName, 
   (Handle *)&preferences) 
 &&
 ((**preferences).signature == kSignature)) {
 globPtr->show12Hour = (**preferences).show12Hour;
 }

 globPtr->nextTick = 0;   // Do first update right away
 globPtr->width = 0;
 globPtr->displayTime = 0;// Haven't displayed a time yet

 HUnlock((Handle)globHand); // Unlock the globals

 result = (long)globHand; // Return the handle to the 
 // globals as the result

done:
 return(result); // Return either a handle or 
 // an error code
}


CleanUp
void CleanUp(GlobalHandle globHand)
{
 GlobalPtrglobPtr;

 if ((long)globHand <= 0) return;

 HLock((Handle)globHand);
 globPtr = *globHand;

 if (globPtr->arrowPicture) 
 DisposeHandle((Handle)globPtr->arrowPicture);

 if (globPtr->configMenu) 
 DisposeMenu(globPtr->configMenu);

 if (globPtr->helpStrings) 
 DisposeHandle(globPtr->helpStrings);

 DisposeHandle((Handle)globHand);
}



HandleMouseClick

long HandleMouseClick(GlobalPtr globPtr, Rect *statusRect)
{
 short  menuItem;
 long   result;
 int    new_width;
 Booleanmode_changed;

 // Check off the appropriate items in the popup menu

 if (globPtr->show12Hour) {
 SetItemMark(globPtr->configMenu, k12HourCmd, 
  sdevMenuItemMark);
 SetItemMark(globPtr->configMenu, k24HourCmd, noMark);
 } else {
 SetItemMark(globPtr->configMenu, k24HourCmd, 
  sdevMenuItemMark);
 SetItemMark(globPtr->configMenu, k12HourCmd, noMark);
 }

 result = 0;

 // Display the popup menu

 menuItem = SBTrackPopupMenu(statusRect, 
  globPtr->configMenu);

 // Handle the menu selection

 mode_changed = false;

 switch (menuItem) {
 case k12HourCmd:
 if (!globPtr->show12Hour) {
 globPtr->show12Hour = true;
 mode_changed = true;
 }
 break;

 case k24HourCmd:
 if (globPtr->show12Hour) {
 globPtr->show12Hour = false;
 mode_changed = true;
 }
 break;
 }

 // If the mode changed, calculate new display width 
 // and let CS know what happened

 if (mode_changed) {
 result = (1 << sdevNeedToSave) 
 | (1 << sdevHelpStateChange);
 new_width = DrawDisplay(globPtr, statusRect, false);
 if (globPtr->width != new_width) {
 globPtr->width = new_width;
 result |= (1 << sdevResizeDisplay);
 }
 }

 return(result);
}


SavePreferences
short SavePreferences(GlobalPtr globPtr)
{
 short  result;
 SavedSettings **preferences;
 Str255 prefsResourceName;

 preferences = (SavedSettings**)NewHandle(                     
 sizeof(SavedSettings));

 if (! (result = MemError())) {  // Allocate a block to hold the settings

 // Include a signature to verify it’s ours
 (**preferences).signature = kSignature; 

 (**preferences).show12Hour = globPtr->show12Hour;

 // Get the name of the preferences resource
 SBGetDetachedIndString(prefsResourceName, 
 globPtr->helpStrings, kPrefNameStr);

 // Save the settings in the Control Strip's preferences file
 result = SBSavePreferences(prefsResourceName, 
 (Handle)preferences);

 DisposeHandle((Handle)preferences); // Get rid of the block
 }

 return(result);
}



UpdateTime

// Compute the current time in seconds since midnight. If it's changed 
since we
// last displayed the time, return true.

Boolean UpdateTime(GlobalPtr globPtr)
{
 unsigned long now;
 int    dispTime;

 GetDateTime(&now);// Get seconds since epoch

// Compute minutes since midnight
 dispTime = (now % (60 * 60 * 24)) / 60;     

// Has the time changed yet?
 if (dispTime != globPtr->displayTime) {                       
 globPtr->displayTime = dispTime;  // Yes
 return(true);   // Need to update display
 } else {
 return(false);
 }
}


NumStr
// Stuff the ascii string representing the number in to the destination 
string.
// Number range is 0 - 99. If pad is true, pad with a zero if necessary.
// Return pointer to end of string.

char *NumStr(char *dest, int num, Boolean pad)
{
 if (num < 0) 
 num = 0;
 if (num > 99) 
 num = 99;
 if (num >= 10) {
 *dest++ = (num / 10) + '0';
 num %= 10;
 } else if (pad) {
 *dest++ = '0';
 }
 *dest++ = num + '0';
 *dest = '\0';
 return(dest);
}



DrawDisplay
// Draw the time specified in displayTime. If drawit is false, don't 
actually
// do any drawing. Returns the width of the display

int DrawDisplay( GlobalPtr globPtr, Rect *statusRect, 
 Boolean drawit)
{
 int    result;
 char   buf[10], 
 *bptr;
 int    hours, minutes;
 Booleanafternoon;
 int    width, offset;
 Rect   arrowRect;

 result = 0;

 hours = globPtr->displayTime / 60;
 if (globPtr->show12Hour) {
 afternoon = (hours >= 12);
 if (afternoon) 
 hours -= 12;
 if (hours == 0) 
 hours = 12;
 }
 minutes = globPtr->displayTime % 60;

 bptr = buf;

 if (globPtr->show12Hour) {
 bptr = NumStr(bptr, hours, false);
 *bptr++ = ':';
 bptr = NumStr(bptr, minutes, true);
 *bptr++ = (afternoon) ? 'P' : 'A';
 *bptr++ = 'M';
 *bptr = '\0';
 } else {
 bptr = NumStr(bptr, hours, true);
 *bptr++ = ':';
 bptr = NumStr(bptr, minutes, true);
 *bptr = '\0';
 }
 c2pstr(buf);

 // Draw the time string a little away from the right edge and centered 
vertically
 // Compute top/bottom margin. -1 is tweak to make it look just right...
 TextFont(DISPLAY_FONT);
 TextSize(DISPLAY_FONT_SIZE);
 TextFace(DISPLAY_FONT_FACE);
 if (drawit) {
 offset = (statusRect->bottom - statusRect->top 
 - globPtr->fontHeight) / 2 - 1;
 MoveTo(statusRect->left + DISPLAY_MARGIN, 
 statusRect->top + offset + globPtr->fontHeight);
 DrawString(buf);
 }

 width = DISPLAY_MARGIN + StringWidth(buf) - 1;
 
 // Draw the right arrow to show that the module has a popup menu
 if (drawit) {
 arrowRect.left = statusRect->left + width;
 arrowRect.right = arrowRect.left + globPtr->arrowWidth;
 arrowRect.top = statusRect->top +
 (statusRect->bottom - statusRect->top 
 - globPtr->arrowHeight) / 2;
 arrowRect.bottom = arrowRect.top + globPtr->arrowHeight;
 DrawPicture(globPtr->arrowPicture, &arrowRect);
 }

 width += globPtr->arrowWidth;

 return(width);
}


CheckFeatures
// Check if this machine is capable of running this control strip (probably
// by using Gestalt). This simple example will run on any Mac, so just 
return
// true.

Boolean CheckFeatures(void)
{
 return(true);
}








  
 

Community Search:
MacTech Search:

Software Updates via MacUpdate

Spotify 1.2.0.1165 - Stream music, creat...
Spotify is a streaming music service that gives you on-demand access to millions of songs. Whether you like driving rock, silky R&B, or grandiose classical music, Spotify's massive catalogue puts... Read more
Thunderbird 102.5.1 - Email client from...
As of July 2012, Thunderbird has transitioned to a new governance model, with new features being developed by the broader free software and open source community, and security fixes and improvements... Read more
Pinegrow 7.03 - Mockup and design web pa...
Pinegrow (was Pinegrow Web Designer) is desktop app that lets you mockup and design webpages faster with multi-page editing, CSS and LESS styling, and smart components for Bootstrap, Foundation,... Read more
Adobe After Effects 2022 23.1 - Create p...
The new, more connected Adobe After Effects can make the impossible possible. Get powerful new features like a Live 3D Pipeline that brings CINEMA 4D scenes in as layers - without intermediate... Read more
SteerMouse 5.6.7 - Powerful third-party...
SteerMouse is an advanced driver for USB and Bluetooth mice. SteerMouse can assign various functions to buttons that Apple's software does not allow, including double-clicks, modifier clicks,... Read more
Wireshark 4.0.2 - Network protocol analy...
Wireshark is one of the world's foremost network protocol analyzers, and is the standard in many parts of the industry. It is the continuation of a project that started in 1998. Hundreds of... Read more
Adobe Premiere Pro 2022 23.1 - Digital v...
Adobe Premiere Pro is available as part of Adobe Creative Cloud for as little as $54.99/month. The price on display is a price for annual by-monthly plan for Adobe Premiere Pro only. Adobe Premiere... Read more
1Password 8.9.10 - Powerful password man...
1Password is a password manager that uniquely brings you both security and convenience. It is the only program that provides anti-phishing protection and goes beyond password management by adding Web... Read more
FotoMagico 6.3 - Powerful slideshow crea...
FotoMagico lets you create professional slideshows from your photos and music with just a few, simple mouse clicks. It sports a very clean and intuitive yet powerful user interface. High image... Read more
Affinity Photo 1.10.6 - Digital editing...
Affinity Photo - redefines the boundaries for professional photo editing software for the Mac. With a meticulous focus on workflow it offers sophisticated tools for enhancing, editing and retouching... Read more

Latest Forum Discussions

See All

‘Awaken Legends: Idle RPG’ Celebrates th...
Awaken Legends: Idle RPG is adding its first update since the game was soft-launched in November, letting players get their hands on a new hero “Hera Valen". Players can also look forward to the Covenant of the Dark Knight event and the Wishing Well... | Read more »
‘Horizon Chase 2’ Japan World Tour Expan...
Horizon Chase 2 () from Aquiris is getting a major expansion today on Apple Arcade. The Japan World Tour expansion brings in 11 new races across 9 cities and it should be rolling out now as of this writing. I expect it to be available worldwide... | Read more »
Dark Fantasy Visual Novel ‘The 13th Mont...
Originally announced for release in August, The 13th Month from Japanese developer Kobayashimaru and publisher Kodansha released on PC via Steam worldwide this month. The dark fantasy visual novel that reimagines the classic Sleeping Beauty tale, is... | Read more »
Tom Clancey’s The Divison Resurgence ann...
Ubisoft has announced the latest Live Test dates for Tom Clancy’s The Division Resurgence, the hotly anticipated mobile entry in the Divison series. Starting December 8th and ending on the 22nd, the test will offer a huge amount of content for the... | Read more »
‘Easy Come Easy Golf’ New Update Adds St...
Easy Come Easy Golf () from Clap Hanz is one of my favorite games on Apple Arcade. It has been updated quite a bit since launch bringing in new modes and improvements. It recently launched on Nintendo Switch as well. | Read more »
Out Now: ‘Magic vs Metal’, ‘Suzerain’, ‘...
Each and every day new mobile games are hitting the App Store, and so each week we put together a big old list of all the best new releases of the past seven days. Back in the day the App Store would showcase the same games for a week, and then... | Read more »
SwitchArcade Round-Up: Reviews Featuring...
Hello gentle readers, and welcome to the SwitchArcade Round-Up for December 7th, 2022. Today can be accurately described as Mikhail Madness, with a whopping four reviews from our pal-est of pals. Football Manager 2023 Touch, Wobbledogs, Soccer Story... | Read more »
Alchemy Stars celebrates 1 and a half ye...
It has been one and a half years since Alchemy Stars launched, and Level Infinite is celebrating in style with a host of new content. There will be a new story mission and even a store to explore, and a whole new mode for those budding idol... | Read more »
Fighting Game ‘Art of Fighting 2’ ACA Ne...
Last week, side-scrolling shooter Pulstar hit mobile platforms as the newest ACA NeoGeo series release from Hamster and SNK. Read Shaun’s review of it here. Today, fighting game Art of Fighting 2 has launched on iOS and Android. Art of Fighting 2... | Read more »
‘Genshin Impact’ Version 3.3 Update Now...
HoYoverse recently revealed the next major update for Genshin Impact (Free) in the form of version 3.3 ‘All Senses Clear, All Existence Void’. | Read more »

Price Scanner via MacPrices.net

New! Details on Verizon’s Christmas/Holiday p...
Verizon is offering discounts on iPhones, Apple Watch models, and iPads with specific promo codes as part of their Christmas/Holiday 2022 offerings. Codes are valid when adding a new line of service... Read more
Apple MagSafe accessories are back on Holiday...
Amazon has Apple MagSafe Chargers and Apple’s MagSafe Battery on sale for up to 24% off MSRP again as part of their Christmas/Holiday sale. Shipping is free, and all models are in stock: – MagSafe... Read more
13″ M2 MacBook Airs on sale again for the low...
Amazon has 13″ MacBook Airs with M2 CPUs in stock today and on sale for $150 off MSRP as part of their Christmas/Holiday Sale, prices start at $1049. Shipping is free. They are the lowest prices... Read more
Get an Apple 16″ MacBook Pro for $400 off MSR...
16″ MacBook Pros with Apple’s M1 Pro CPUs are in stock and on sale today at B&H Photo for $300-$400 off Apple’s MSRP for a limited time. Prices start at $2099 for M1 Pro models with 512GB or 1TB... Read more
Holiday clearance sale! Previous-generation A...
Amazon has 2nd generation 32GB and 64GB 4K Apple TVs with Siri remotes and 32GB Apple TV HDs on clearance sale for $80-$90 off original MSRP. Shipping is free, and delivery is available in time for... Read more
Christmas sale at Verizon: Apple AirPods Pro...
Verizon has first-generation Apple AirPods Pro on sale for $159.99 on their online store as part of their continuing Christmas/Holiday sale. Their price is $90 off Apple’s original MSRP, and it’s the... Read more
New Christmas/New Years promo at Xfinity Mobi...
Switch to Xfinity Mobile and open a new line of service, and take $400 off the price of a new iPhone, no trade-in required, through January 10, 2023. The $400 is applied to your account as credits... Read more
Apple iPad Smart Keyboard Folio prices drop u...
Apple iPad Smart Keyboard Folio prices have dropped up to $60 off MSRP at Amazon and Walmart as part of their Christmas/Holiday sales. These are the cheapest prices currently available for these iPad... Read more
Today is the final day for Xfinity Mobile’s $...
If you switch to Xfinity Mobile and open a new line of service, they will take $500 off the price of a new iPhone, no trade-in required. This is the best no trade-in Cyber Monday Apple iPhone 14 deal... Read more
Amazon restocks 10.2″ 64GB 9th-generation iPa...
Amazon has Apple’s 9th generation 10.2″ 64GB WiFi iPads (Silver) in stock and on sale for $269.99 shipped as part of their Christmas/Holiday Sale. Their price is $60 off Apple’s MSRP. Free delivery... Read more

Jobs Board

*Apple* Systems Administrator - JAMF - Activ...
…Administration **Duties and Responsibilities** + Configure and maintain the client's Apple Device Management (ADM) solution. The current solution is JAMF supporting 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
Omnichannel Associate - *Apple* Blossom Mal...
Omnichannel Associate - Apple Blossom Mall Location:Winchester, VA, United States (https://jobs.jcp.com/jobs/location/191170/winchester-va-united-states) - Apple Read more
Sephora Beauty Advisor - *Apple* Blossom Ma...
Sephora Beauty Advisor - Apple Blossom Mall Location:Winchester, VA, United States (https://jobs.jcp.com/jobs/location/191170/winchester-va-united-states) - Apple 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
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.