Undo, TCommand
Volume Number: | | 6
|
Issue Number: | | 11
|
Column Tag: | | Jorg's Folder
|
TCommand and Undo
By Jörg Langowski, MacTutor Editorial Board
MacApp - TCommand and Undo
The example MacApp program in the August and September columns gives us a starting point for explaining how to extend a MacApp application. One of the most important operations that well-written Macintosh programs should support is Undo; so in this column I will show you in more detail how to implement undoing of commands in MacApp.
To undo an operation done on some document, we have to remember the state of the document before the operation and restore that state. Sounds simple; the problem is that in a usual Macintosh application many parts of the program will be affected. The structure beneath MacApp, however, makes it very simple to implement Undo. For each operation that should be undoable, a command object is created which is intelligent enough to remember what it has done to the document, and which contains an Undo method that uses this information to reverse the operation.
Using command objects
Before we review our particular command objects methods and variables, lets see how some of these command objects are used. When the mouse is clicked inside a MacApp view, the DoMouseCommand method of that view is called. In your definition of that method, you must define the mouse behavior that you want. The previous example knew only one behavior; when the drawing icon in the palette was selected, one could draw a rounded rectangle, using a cross cursor.
The standard way of implementing the mouse behavior would then be:
- determine which command you want to execute, depending on where the mouse was clicked;
- create a new command object corresponding to the operation to be done, and check for errors with FailNIL;
- initialize the command object by calling its initialization method;
- and, finally, exit the DoMouseCommand method, returning the command object to the calling routine.
That command object is then used by MacApp to track the mouse and implement undo/redo. When it is no longer used, it will be deleted (so you dont have to care about it anymore).
In our new example, we want to implement dragging of the rectangles. When the mouse is clicked inside one of the rectangles, moving it should not create a new rectangle, but drag the old one around. Therefore, we first have to write a routine that checks whether the mouse was clicked inside an existing object. This is done by a global routine, FindBox, which is used as a parameter to the ForEachShapeDo method of the TEDocument class, passing the parameters to FindBox through the structure aFindBoxStruct. (The way in which a routine can be applied to a list of shapes has been described in the previous example - C++ makes it a little more complicated than Pascal).
When the mouse has been clicked inside an existing shape (aFindBoxStruct.myBox is non-nil), we use the Dragger instead of the Sketcher object to implement the mouse behavior (see listing).
The TCommand class
Command objects are implemented through MacApps TCommand class. If you want to define some undoable operation, you have to derive a subclass of TCommand which implements that specific operation. The class TDragger is implemented below. It includes the methods IDragger, TrackMouse, DoIt, UndoIt, and RedoIt.
In DoMouseCommand, we first create a new TDragger object, and then initialize it, telling it which object is going to be dragged (itsBox). In the initialization method, that objects pointer is copied into an instance variable (fBox), and the instance variables oldLocation and newLocation are set to their initial values.
After we return the Dragger object from our DoMouseCommand, the MacApp system will call its TrackMouse method. The variable aTrackPhase indicates whether we just pushed the mouse button, whether we are in the middle of a drag, or just released the button. We need to take action only after the button has been released; it is then that the shape is moved to its new location on the screen. We set the objects coordinates to their new values (calculated from the starting and ending points of the mouse drag), change newLocation, and return from the routine. this is returned to the calling routine, which means that on the next call the same mouse tracker will be used.
Note that all we need to do in the mouse tracker is to change the coordinates of the dragged object. The actual move will be done by the DoIt method, which is called after the mouse drag is completed. DoIt simply invalidates the objects old and new bounds rectangles, so that these regions will be updated (this is also done automatically by MacApp).
In UndoIt, we simply reset the coordinates back to the old location and then call DoIt; RedoIt changes the coordinates back to the new location and DoesIt.
So in fact, you see that undoing a simple operation like moving an object is made very simple by MacApp. The command object exists as long as no other undoable command is chosen; when you perform another action that might be undoable, MacApp frees the last command so that its information is lost. But before that, all parameters necessary to undo/redo the operation should be stored inside the command object and used if necessary.
A final remark to the cmnu 128 resource: This is a pseudo-menu (never displayed in the menu bar), which contains buzzwords that should appear after Undo in the Edit menu so that the user can see which command can be undone/redone. The buzzword is associated with the proper command through the command number, we define cDragBox = 3001 for this purpose. This definition must of course be included in both the Rez file and the C++ program. It is used by the ICommand method, where the menu behavior is initialized.
When you execute the example and drag one of the rectangles around, you might notice that the mouse behavior is somewhat strange. The object is not dragged by moving its gray outline around, as you would expect, but instead a rubber band rectangle is drawn connecting the starting and ending points of the drag. This is the standard behavior of mouse move feedback in MacApp, and if we want something more fancy, we have to define it ourselves. Next month, Ill show you how to implement such a track feedback routine. Until then, happy hacking.
Listing 1: Changes to the V6#8 example to support shape dragging
class TDragger : public TCommand {
public:
TTEDocument *fTEDocument;
TTextView*fTextView;
TBox *fBox; // the object being dragged
Rect oldLocation; // initial location of object
Rect newLocation; // new location of object
pascal void IDragger(TBox *itsBox,
TTEDocument *itsDocument, TTextView *itsView);
pascal struct TCommand *TrackMouse
(TrackPhase aTrackPhase,
VPoint *anchorPoint, VPoint *previousPoint,
VPoint *nextPoint, Boolean mouseDidMove);
pascal void DoIt();
pascal void RedoIt();
pascal void UndoIt();
#ifdef qDebug
virtual pascal void Fields
(pascal void (*DoToField) (StringPtr fieldName,
Ptr fieldAddr, short fieldType, void *link),
void *link);
#endif
};
struct FindBoxStruct {
Point theMouse;
TBox *myBox;
};
const int cDragBox = 3001;
// command number for Box dragger object}
pascal void FindBox
(TBox *aBox, FindBoxStruct *aFindBoxStruct)
{
if (PtInRect
(aFindBoxStruct->theMouse,&aBox->fLocation))
{ aFindBoxStruct->myBox = aBox; };
}
pascal struct TCommand *TTextView::DoMouseCommand
(Point *theMouse, EventInfo *info, Point *hysteresis)
{
TSketcher *aSketcher;
TDragger *aDragger;
FindBoxStruct aFindBoxStruct;
if (fPaletteView->fIconSelected == kBox-kBox)
{
// dragging support, JL 9/90
aFindBoxStruct.theMouse = *theMouse;
aFindBoxStruct.myBox = nil;
fTEDocument->ForEachShapeDo
((DoToObject)FindBox,&aFindBoxStruct);
if (aFindBoxStruct.myBox != nil)
{
SysBeep(5);// drag it
aDragger = new TDragger;
FailNIL(aDragger);
aDragger->IDragger(aFindBoxStruct.myBox,
fTEDocument, this);
return aDragger;
}
else
{
aSketcher = new TSketcher;
FailNIL(aSketcher);
aSketcher->ISketcher(fTEDocument, this);
return aSketcher;
}
}
else
return inherited::DoMouseCommand
(theMouse,info,hysteresis);
}
pascal void TDragger::IDragger
(TBox *itsBox, TTEDocument *itsDocument,
TTextView *itsView)
{
TScroller *aScroller;
aScroller = itsView->GetScroller(true);
ICommand(cDragBox, itsDocument,
itsView, aScroller);
fTEDocument = itsDocument;
fTextView = itsView;
fBox = itsBox;
oldLocation = fBox->fLocation;
newLocation = fBox->fLocation;
}
pascal struct TCommand *TDragger::TrackMouse
(TrackPhase aTrackPhase, VPoint *anchorPoint,
VPoint *previousPoint, VPoint *nextPoint,
Boolean mouseDidMove)
{
if ((aTrackPhase == trackRelease)
&& mouseDidMove)
{
newLocation.top = oldLocation.top
+ nextPoint->v - anchorPoint->v;
newLocation.left = oldLocation.left
+ nextPoint->h - anchorPoint->h;
newLocation.bottom = oldLocation.bottom
+ nextPoint->v - anchorPoint->v;
newLocation.right = oldLocation.right
+ nextPoint->h - anchorPoint->h;
fBox->fLocation = newLocation;
}
return this;
}
pascal void TDragger::DoIt()
{
fTextView->InvalidRect(&newLocation);
fTextView->InvalidRect(&oldLocation);
}
pascal void TDragger::RedoIt()
{
fBox->fLocation = newLocation;
DoIt();
}
pascal void TDragger::UndoIt()
{
fBox->fLocation = oldLocation;
DoIt();
}
#ifdef qDebug
pascal void TDragger::Fields(pascal void (*DoToField)
(StringPtr fieldName, Ptr fieldAddr,
short fieldType, void *link), void *link)
{
DoToField(\pTDragger, nil, bClass, link);
DoToField(\pfTEDocument,
(Ptr) &fTEDocument, bObject, link);
DoToField(\pfTextView,
(Ptr) &fTextView, bObject, link);
DoToField(\pfBox, (Ptr) &fBox, bObject, link);
DoToField(\poldLocation,
(Ptr) &oldLocation, bRect, link);
DoToField(\pnewLocation,
(Ptr) &newLocation, bRect, link);
inherited::Fields(DoToField, link);
}
#endif
#define cDragBox 3001
resource cmnu (128) {
128,
textMenuProc,
allEnabled,
enabled,
Buzzwords,
/* these words appear after Undo in the Edit menu */
{
Page Setup Change, noIcon, noKey,
noMark, plain, cChangePrinterStyle;
Typing, noIcon, noKey, noMark, plain, cTyping;
Drawing, noIcon, noKey,
noMark, plain, cDrawBox;
Dragging, noIcon, noKey,
noMark, plain, cDragBox
}
};