TweetFollow Us on Twitter

Forth DA
Volume Number:3
Issue Number:2
Column Tag:Threaded Languages

Building Desk Accessories with Forth

By Jörg Langowski, MacTutor Editorial Board, Grenoble, France

A template desk accessory in Mach2

Any of our readers who has taken a close look at Mach2 code will have noticed that the output generated by the Forth compiler resembles very much that of 'classical' compiled languages like Pascal. Disassembly shows that much of the code is inline-generated machine code, and references to kernel routines are not too frequent.

This is one of the strong points of Mach2; retaining most of the ease of programming and debugging with a Forth interpreter, you can not only generate stand-alone applications, but also things that are much more dependent on interacting directly with the operating system such as VBLtasks that run independently of a runtime Forth kernel (see my article in V2#6 ); one could also imagine to create INIT resources, MDEFs or WDEFs and... desk accessories.

The problem with Forth code in general is that a 'stand-alone-application' generated by any Forth system available for the Macintosh contains - and is dependent on - at least part of the run time Forth kernel. Whether the kernel contains the interpreter (as in MacForth) or the task of interpreting is taken over by the CPU itself in subroutine threaded code such as Mach2 - the standard I/O routines, window handling, controls, menus etc. all come in a pre-written package that will form part of the stand-alone application. To write something like a desk accessory in Forth, this would imply that the runtime package had to be part of the DA. This is (a) not very practical because space-consuming and (b) not an available option in any Forth for the Macintosh that I'm aware of.

Nevertheless, Mach2 allows us to create a functioning desk accessory without too much effort and allows me to simultaneously illustrate some principles of DA programming to you at the same time.

DA strategy for implementation in Mach2

How would we proceed to build a desk accessory using Mach2? The DA is a DRVR resource. We would have to create this resource in memory first, then write it out to a resource file. There are resource manager routines that allow us to do this; AddResource will add a new resource to the current resource file, given a handle to a data structure in memory, and UpdateResFile saves these changes to the resource file. So all we have to do is to create a data structure of the format of a desk accessory, get a handle to it and call AddResource with the type DRVR to create the new driver, then update the resource file.

The general format of a desk accessory is known from Inside Macintosh. The first couple of bytes are a header containing flags that tell the system whether the DA needs to be called periodically, and what type of calls it can respond to; a delay setting that determines the time between periodic actions; and event mask that determines what events the desk accessory will respond to; a menu ID (negative) if the DA has a menu associated with it; and offsets to the Open, Prime, Control, Status and Close routines. These latter offsets are measured from the beginning of the desk accessory to the beginning of each of the routines. The last portion of the header is a string containing the driver name.

The remaining portion of the desk accessory may be executable code and can be written in Mach2 Forth if we make sure that references to kernel routines are avoided. Before we discuss the example (listing 1), however, let me briefly summarize what happens when a desk accessory is opened.

Fig. 1 Our simple DA, written in Forth!

Opening the desk accessory

When the DA (or any driver) is opened for the first time, a device control entry is created by the system, a data structure which contains information about the driver; it is described in Inside Macintosh (II-190). It will, for instance, contain the driver flags, the delay setting, the event mask and the menu ID from the desk accessory header. Also a window pointer to a window associated with the driver may be stored here or a handle to a memory block if the DA needs to store large amounts of data.

When a driver routine (open, control, close, status, prime) is called, a pointer the driver's device control entry is passed in register A1. The other parameter, passed in A0, is a pointer to the parameter block of the call. For desk accessories, this parameter block is important for Control calls since we'll be able to tell from the parameter block what has happened that the desk accessory has to respond to, such as menu selections, periodic actions, editing commands, etc.

Glue routines

Since the parameters to the driver routines are passed in registers, we'll have to write some assembler code to make them 'digestible' for Forth, which is stack-oriented. Also, we'll save A0-A1 and restore them after the call; as IM mentions, no other registers have to be saved. One important thing to remember is that we have to setup a Forth stack before using any actual Forth code; we make A6 point to a data block sufficiently large (100 bytes in the example, but you may easily change this to have more stack space).

The glue routines then in turn call the driver routines which have been written in Forth. The routines referenced in the DA header are the glue routines, of course. The final part of listing 1 contains the stack setup, the glue routines, and the part that initializes the desk accessory header and writes the driver code to a resource file.

The code written is contained between the 'markers' startDA and endDA. For adding the resource to the file, the word make-res is provided, which gets a handle to a data structure in memory and calls AddResource with the handle, the resource type (DRVR in our case) and a resource file ID as parameters.

init-DA will initialize the desk accessory's header. This includes setting the driver flags, the driver name, an event mask, the delay time between periodic actions, and calculating and storing the offsets between the start of the DA and the beginning of the 'glue' routines. Also, the ID of the DA's own menu is stored in the header; we'll come back to that later.

make-DA calls init-DA and then writes the newly created DRVR resource with ID=12 into the file "Mach2 DA.rsrc". This file can then be used by RMaker to create a Font-DA Mover compatible file that contains the DA and any resources owned by it.

DA-owned resources

Listing 2 shows the RMaker input file. It will include the DRVR code from "Mach2 DA.rsrc" and two more resources, a window template and a menu. Both these resources have an ID of -16000, which later indicates to the Font/DA Mover that they are 'owned' by the desk accessory whose ID is 12; they will therefore be moved together with the DA. If the DA's ID is changed during the move, their IDs will be changed accordingly so that they always correspond to that of the DA.

The format of the ID number of an owned resource is given in IM (I-109); I'll briefly review it here. The ID number is always negative and bits 15 and 14 are always 1. Bits 11-13 specify the owning resource type, and are zero for a DRVR. Bits 5-10 contain the ID number of the owning resource, which therefore must be between 0 and 63. Bits 0-4 may contain a number which identifies the individual resource. Therefore, the allowed number range for owned resources is between -16384 and -1.

If the DRVR resource has an ID=12, the IDs of the owned resources start with -16000 ( if bits 0-4 are zero) and go up to -15969 ( bits 0-4 = 31). Since -16000 is a simple number to remember, the DRVR is given an ID of 12 when it is created by the program. Both the MENU and WIND resources owned by the DRVR in the example will have IDs of -16000 (which correspond to 'local' IDs of 0).

Two Forth words are provided to easily convert local IDs to owned resource IDs. getDrvrID will calculate the driver ID from its reference number, which is kept in the device control entry; and ownResID will calculate the owned resource ID from the driver ID and the local resource ID.

The desk accessory

We can now take a look at the desk accessory's main code. The Open routine is called by the DAOpen glue routine. It will do nothing if the desk accessory's window is already open, which can be checked by looking at the dCtlWindow field in the device control entry. If the DA has not been opened yet, or has been opened and then closed again, it will create a new window from the WIND resource with local ID=0 and store its pointer in the device control entry; furthermore, it stores the driver reference number in the windowKind field of the window record. By this means, the desk manager will know that a window belongs to the DA, how to find it and to send the appropriate messages to the DA when the window is activated, deactivated, the mouse clicked in its content region or when it is closed.

Open will in addition calculate the ID of the MENU resource (local ID=0) that is owned by the DA. This number is also stored in the DA header, but you cannot reliably assume that it is correct. Font/DA Mover will change the DA's ID and the IDs of its own resources correctly, but it doesn't go into the DA header and sets the correct menu ID. However, some negative menu ID has to be present in the DA header in order to tell the desk manager that the DA has to respond to menu selections. The device control entry, however, has to contain the correct menu ID; otherwise the DA won't respond to its own menu.

Close will store zero in the dCtlWindow field so that a new Open will re-create the window; it deletes the DA's menu and disposes of the heap space occupied by window and menu, then it redraws the menu bar. Close is called automatically by the Desk Manager when the close box of the DA window is clicked, or Close is selected from the File menu of an application where the DA was called.

The Prime and DrStatus routines are not needed here, and will do nothing at all.

Sending messages to the DA

The heart of the desk accessory is the Ctl routine. This routine will receive a message from the desk manager to indicate which action should be taken - a very simple implementation of object-oriented behavior, in fact. I have written a shell routine that handles some of the actions of a desk accessory; all other actions simply do nothing, but since they are included in the case statement, you can very easily add your own routines.

The message code is contained in the csCode parameter, which is in the parameter block whose address was passed in A0 when Ctl was called. Ten messages are possible:

-1 : 'good bye kiss' that will be given just before an application exits to the finder;

64 : an event should be handled;

65 : take the periodic action that has to be performed by the DA. This message is sent every time the number of ticks in the drvrDelay field of the DA header has expired;

66 : The cursor shape should be checked and changed if appropriate. This message is sent each time SystemTask is called by the application, as long as the DA is active;

67 : A menu selection should be handled. csParam contains the menu ID and csParam+2 the menu item number;

68 : handle Undo command from the Edit menu;

70 : handle Cut command;

71 : handle Copy command;

72 : handle Paste command;

73 : handle Clear command.

The example implements handlers for the first five actions; no Edit menu selections are handled. The periodic action simply consists of a short beep once every second. (You might want to change this to save your sanity if you really want to do something useful with this desk accessory). The goodBye action is also a beep, but 50 ticks long. When the desk accessory is active and you close an application, it will sound almost as if the system reboots. Don't let yourself be bothered by this.

The accCursor message will call update-cursor, which checks whether the mouse is inside the DA window and changes the cursor to the standard NNW arrow, if necessary.

The menu and event handlers are a little more complicated. First, since both will output text to the DA window, we have to write some rudimentary output routines; the Mach2 output routines won't work without the kernel. tp will type a string in the current grafPort, and crd acts the same way as cr in the Forth kernel. I've also included some numeric output routines, which you might find convenient to use; they are not needed for the example, although I used them in debugging.

The event handler(s)

The DA's response to the accEvent message has to be subdivided according to the event that has happened. Therefore, we check the what field of the event record and set up another case statement that contains the handlers for each type of event. The behavior that we'll give to our DA window is that of a document window with zoom box and size box that responds to mouse down and key down events by displaying appropriate messages in the window. The DA's own menu should be displayed when the window is activated and removed when it is deactivated.

The activate handler, therefore, first checks whether the window is activated or deactivated, gets the menu from the resource file in the first case and attaches it to the menu bar, or deletes it in the latter case.

The update handler will clear the update region and redraw the grow icon. Key down events will clear the window and display a message in the first line.

Mouse down events cannot be handled as easily as with application windows. If you call findWindow when the mouse is clicked in a desk accessory window, the code returned is always 2 (= in system window), no matter what part of the system window was clicked. The drag region and close box are handled by the desk manager, so no problem there; but we have to check ourselves for clicks in the size or zoom box. This is especially annoying for the zoom box, because we also have to keep a record of the current zoom state of the window. With application windows, the window manager takes care of this task, changing the part code that is returned by FindWindow depending on whether we have to zoom in or out.

I defined the words ?inGrow and ?inZoom that return true when the mouse click (in local coordinates) was in the size box or in the zoom box of the active window. The zoom state has to be maintained by a flag. The mouse down event handler will check for size box and zoom box clicks and change the window accordingly. The region that comprises the grow icon - which is part of the content region - will have to be added to the update region after the window has been made smaller or before it is enlarged. The word invalsize has been defined for this purpose; for resizing with the size box, we just call it before and after the resizing since we don't know the new window size. For zooming, we call invalsize before zooming in and after zooming out.

If the mouse is clicked in the content region, the window responds simply by typing a message, followed by a new line.

This takes care of mouse down events; now menus are the last thing we have to include. If the accMenu message is received by the DA, the menu item number is extracted from the parameter block and a message displayed according to the item number. Add any of your own routines here if you like.

Getting the DA started

To add the desk accessory to your system file, just load the Forth program and type make-DA. This will create a file "Mach2 DA.rsrc" on the default disk. Then run RMaker with the input given in listing 2, which will give you a small briefcase called "Mach2 DA". It contains the DRVR, MENU and WIND resources and may be used as an input to the Font/DA Mover to install the desk accessory in the system file. Good luck (you don't really need it, though).

Using the template to write 'useful' DAs

In the unlikely case that you would want to beef up the DA example to do something really useful, you should be careful about a couple of things.

First, make sure that no Forth word you use in yout routines makes part of the Mach2 kernel. This can easily be checked by including the word in a simple definition and disassembling it. If you see a JSR to a jump table entry or a JSR xxx(A5) at the position of the word, you can't use it in a DA. JSRs are only legal if they point to routines that you defined yourself. The only Mach2 words you may use are those that directly compile 68000 code; fortunately, there are quite a few of them. Some others you have to redefine: the multiply and divide operators, for example.

Second, A6 stack space may become a problem if your routines get more complicated. This is easily taken care of, but equally easy to overlook.

Third, if you redefine any general purpose routines that create kernel-independent code and could be useful to others in writing their DAs, don't hesitate to drop me a line. Nothing is more frustrating than having to reinvent the wheel...

{1}
Listing 1: Desk Accessory written in Mach2
( Mach2 desk accessory with owned resources )
( J. Langowski / MacTutor Nov. 86 )

only forth also assembler also mac

HEX
44525652 CONSTANT "drvr

BINARY
0000110111101010 CONSTANT DAEmask

( *** System globals *** )
HEX
8FC CONSTANT JioDone 

DECIMAL
( windowrecord fields, starting with grafport )
16 CONSTANT portRect ( Grafport rectangle )

( fields of WindowPeek )
108 CONSTANT windowKind 
110 CONSTANT wVisible
111 CONSTANT wHiLited
112 CONSTANT goAwayFlag
113 CONSTANT spareFlag
130 CONSTANT dataHandle
140 CONSTANT controlList
152 CONSTANT refCon

( fields of device control entry )
 4 CONSTANT dCtlFlags
 6 CONSTANT dCtlQHdr
16 CONSTANT dCtlPosition
20 CONSTANT dCtlStorage
24 CONSTANT dCtlRefNum
26 CONSTANT dCtlCurTicks
30 CONSTANT dCtlWindow
34 CONSTANT dCtlDelay
36 CONSTANT dCtlEMask
38 CONSTANT dCtlMenu

( csCodes for Ctl calls )
-1 CONSTANT goodBye
64 CONSTANT accEvent
65 CONSTANT accRun
66 CONSTANT accCursor
67 CONSTANT accMenu
68 CONSTANT accUndo
70 CONSTANT accCut
71 CONSTANT accCopy
72 CONSTANT accPaste
73 CONSTANT accClear

( *** standard parameter block data structure *** )
0   CONSTANT  qLink( pointer to next queue entry )
4   CONSTANT  qType( queue type )
6   CONSTANT  ioTrap ( routine trap )
8   CONSTANT  ioCmdAddr ( routine address )
12  CONSTANT  ioCompletion( addr of completion routine )
16  CONSTANT  ioResult  ( result code returned here )
18  CONSTANT  ioNamePtr ( pointer to file name string)
22  CONSTANT  ioVRefNum ( volume reference number )
24  CONSTANT  ioRefNum
26  CONSTANT  csCode ( type of control call )
28  CONSTANT  csParam( control call parameters )

( *** eventrecord data structure *** )
0  CONSTANT what
2  CONSTANT message
6  CONSTANT when
10 CONSTANT where
14 CONSTANT modifiers

( *** event codes *** )
0  CONSTANT null-evt
1  CONSTANT mousedn-evt
2  CONSTANT mouseup-evt
3  CONSTANT keydn-evt
4  CONSTANT keyup-evt
5  CONSTANT autokey-evt
6  CONSTANT update-evt
7  CONSTANT disk-evt
8  CONSTANT activate-evt
10 CONSTANT network-evt
11 CONSTANT driver-evt

CODE shl ( data #bits )
 MOVE.L (A6)+,D0
 MOVE.L (A6),D1
 LSL.L  D0,D1
 MOVE.L D1,(A6)
 RTS
END-CODEMACH

CODE shr ( data #bits )
 MOVE.L (A6)+,D0
 MOVE.L (A6),D1
 LSR.L  D0,D1
 MOVE.L D1,(A6)
 RTS
END-CODEMACH

( *** start of desk accessory main code *** )

header testDA ( marker for writing to DRVR resource )
 header drvrFlags  2 allot
 header drvrdelay  2 allot
 header drvrEMask  2 allot 
 header drvrMenu   2 allot
 header drvrOpen   2 allot
 header drvrPrime  2 allot
 header drvrCtl  2 allot
 header drvrStatus 2 allot 
 header drvrClose  2 allot
 header drvrname  32 allot

( *** main desk accessory routines *** )
header oldPort 4 allot    ( for storage of old grafPtr )
header temprect 8 allot
header SizeRect 8 allot   ( grow size limits )
header mouseLoc 4 allot   ( mouse location )
header NewSize 4 allot    ( for SizeWindow )
header penLoc 4 allot( pen location )
header tempString 256 allot   ( for numeric conversion etc. )
header zoomState 4 allot  ( zoomed in or out )

: whereMouse ['] mouseLoc call getMouse ['] mouseLoc @ ;

: cl  ( WPtr -- ) portrect + call eraserect ;

: tp  call drawstring ;

: crd ['] penLoc call getpen
 10 ( horizontal boundary )
 ['] penLoc w@ 12 +
 call moveto
;

CODE NumToString
 MOVE.L (A6)+,A0
 MOVE.L (A6),D0
 MOVE.W #0,-(A7)
 _Pack7
 MOVE.L A0,(A6)
 RTS
END-CODE

CODE StringToNum
 MOVE.L (A6),A0
 MOVE.W #1,-(A7)
 _Pack7
 MOVE.L D0,(A6)
 RTS
END-CODE

CODE unpack
 MOVE.L (A6),D0
 CLR.L   D1
 MOVE.W D0,D1
 CLR.W  D0
 SWAP.W D0
 MOVE.L D0,(A6)
 MOVE.L D1,-(A6)
 RTS
END-CODE

CODE pack
 MOVE.L (A6)+,D1
 MOVE.L (A6),D0
 SWAP.W D0
 MOVE.W D1,D0
 MOVE.L D0,(A6)
 RTS
END-CODE

: .d ( num -- )  ['] tempstring NumToString  tp  ;
 
( *** event-handling routines *** )

: activate-handler { menuID DAWind event-rec | -- }
 event-rec modifiers + w@ 1 and
 IF ( window activated )
 menuID call getRMenu 0 call InsertMenu  
 call drawMenuBar
 ELSE ( window deactivated )
 menuID call deleteMenu
 menuID call getRMenu call DisposMenu
 call drawMenuBar
 THEN
;
 
: update-handler { DAWind event-rec | -- }
 ['] penLoc call GetPen
 DAWind CALL BeginUpdate
    DAWind cl
    DAWind CALL DrawGrowIcon
 DAWind CALL EndUpdate
 ['] penLoc 2+ w@ ['] penLoc w@ 
 call moveto ( restore pen position )
;

: ?inGrow { localPt WPtr | b r -- flag }
 WPtr portRect + 4 +
 dup w@ -> b 2+ w@ -> r
 ['] temprect r 14 - b 14 - r b call setrect
 localPt ['] tempRect call PtInRect 
;

: ?inZoom { localPt WPtr | r -- flag }
 WPtr portRect + 6 + w@ -> r
 ['] temprect r 20 -   -16   r 8 -   -4 call setrect
 localPt ['] tempRect call PtInRect 
;

: invalSize { gPort | b r -- }
 gPort 4 + w@ -> b
 gPort 6 + w@ -> r
 ['] temprect r 16 - 0 r b call setrect
 ['] temprect call invalrect
 ['] temprect 0 b 16 - r b call setrect
 ['] temprect call invalrect
;

: mousedn-handler { DAWind event-rec | whereM DAPort -- }
 DAWind portrect + -> DAPort
 event-rec where + @ -> whereM
 whereM ['] mouseLoc !
 ['] mouseloc call GlobalToLocal
 ['] mouseloc @ dup 
 DAWind ?inGrow  
 IFDAPort invalSize
 DAWind whereM ['] SizeRect call GrowWindow 
 DAWind swap unpack swap -1 call sizewindow
 DAPort invalSize
 ELSE 
   DAWind ?inZoom
   IF   ['] zoomState @
 IF 0 ['] zoomState !
    DAWind whereM 7 call TrackBox
 IF DAPort invalSize
    DAWind 7 0 call ZoomWindow THEN
 ELSE 1 ['] zoomState !   
    DAWind whereM 8 call TrackBox
 IF DAWind 8 0 call ZoomWindow 
    DAPort invalSize THEN
 THEN
   ELSE ( in content region )
 " Mouse down" tp crd
   THEN
 THEN
;

: update-cursor  { DAWind | -- }
 whereMouse DAWind portrect + call PtInRect
 IF call InitCursor THEN
;

: getDrvrID { dCtlEntry | -- num }
 dCtlEntry dCtlRefNum + w@ l_ext
 1+ negate
;

: ownResID ( resID drvrID )
 5 shl + -16384 +
;

: Open { DCtlEntry ParamBlockRec | DAWind -- }
 ['] oldPort call GetPort
 dCtlEntry dCtlWindow + @
 0= IF ( not open already )
 0 dCtlEntry getDrvrID ownResID 
 dup dCtlEntry DCtlMenu + w! 
 ( menu ref has to be updated )
 0 0 call getNewWindow -> DAWind
 DAWind  dCtlEntry dCtlWindow + !  
 ( store window pointer )
 DAWind  dCtlEntry dCtlRefNum + w@  
 swap windowKind + w!
 DAWind  call setport
 0 ['] zoomState !
 ['] sizerect 50 50 500 320 call setrect
 10 10   call moveto
 ['] oldPort @ call setPort
 THEN
;

: Close { DCtlEntry ParamBlockRec | -- }
 dCtlEntry dCtlWindow + 
 dup @ call DisposWindow  0 swap ! 
 ( so that Open will work again )
 DCtlEntry DCtlMenu + w@ ( get menu ID )
 dup call deletemenu
 call getRMenu call disposMenu call drawMenuBar
;

: Ctl 
  { DCtlEntry ParamBlockRec | DAWind event-rec menuItem -- }

 ['] oldPort call GetPort
 dCtlEntry dCtlWindow + @ dup -> DAWind call setport
 ParamBlockRec csCode + w@ l_ext 
 CASE
 goodByeOF 50 call sysbeep ENDOF
 accEvent OF 
 ParamBlockRec csParam + @ -> event-rec
 event-rec what + w@ 
 CASE
 mousedn-evtOF   
 DAWind event-rec mousedn-handler ENDOF

 keydn-evt OF DAWind cl
 DAWind call DrawGrowIcon
 10 10 call moveto  " Key down." tp crd
 ENDOF

 autokey-evtOF ENDOF

 update-evt OF
 DAWind event-rec update-handler ENDOF

 disk-evt OFENDOF

 activate-evt  OF
  DCtlEntry DCtlMenu + w@ ( get menu ID )
  DAWind event-rec activate-handler  ENDOF

 network-evtOF ENDOF
 driver-evt OF ENDOF

 ENDCASE

 ENDOF

 accRun OF    1 call sysbeep  ENDOF
 accCursor  OF DAWind update-cursor ENDOF
 accMenuOF
 ParamBlockRec csParam + 2+ w@ l_ext
 CASE 1 OF " Item1!" tp crd ENDOF
 2 OF " Item2!" tp crd ENDOF
 3 OF " Item3!" tp crd ENDOF
 4 OF " Item4!" tp crd ENDOF
 6 OF " Item6!" tp crd ENDOF
 ENDCASE
 0 call HiLiteMenu
 ENDOF
 accUndoOFENDOF
 accCut OFENDOF
 accCopyOFENDOF
 accPaste OFENDOF
 accClear OFENDOF
 ENDCASE
 ['] oldPort @ call setPort
;

: DrStatus { DCtlEntry ParamBlockRec | -- }
;

: Prime { DCtlEntry ParamBlockRec | -- }
;

( *** glue routines *** )
header local.stack 200 allot

CODE setup.local.stack
    LEA -8(PC),A6   ( local stack grows downward from here )
    RTS
END-CODE

CODE DAOpen 
 MOVEM.L A0-A1,-(A7)
 setup.local.stack
 MOVE.L  A1,-(A6) 
 MOVE.L  A0,-(A6)
 Open
 CLR.L  D0
 MOVEM.L (A7)+,A0-A1 
RTS END-CODE

CODE DAClose  
 MOVEM.L A0-A1,-(A7)
 setup.local.stack
 MOVE.L  A1,-(A6) 
 MOVE.L  A0,-(A6)
 Close
 CLR.L   D0
 MOVEM.L (A7)+,A0-A1 
RTS END-CODE

CODE DACtl 
 MOVEM.L A0-A1,-(A7)
 setup.local.stack
 MOVE.L  A1,-(A6) 
 MOVE.L  A0,-(A6)
 Ctl
 CLR.L   D0
 MOVEM.L (A7)+,A0-A1
 MOVE.L  JioDone,-(A7) 
RTS END-CODE

CODE DAStatus 
 MOVEM.L A0-A1,-(A7)
 setup.local.stack
 MOVE.L  A1,-(A6) 
 MOVE.L  A0,-(A6)
 DrStatus
 CLR.L   D0
 MOVEM.L (A7)+,A0-A1 
RTS END-CODE

CODE DAPrime 
 MOVEM.L A0-A1,-(A7)
 setup.local.stack
 MOVE.L  A1,-(A6) 
 MOVE.L  A0,-(A6)
 Prime
 CLR.L   D0
 MOVEM.L (A7)+,A0-A1 
RTS END-CODE

header endDA
 ( *** code written to DRVR resource ends here *** )

( *** initialization routines *** ) 

: setFlags  ['] drvrFlags w! ;
: setDelay  ['] drvrDelay w! ;
: setEMask  ['] drvrEMask w! ;
: setMenuID ['] drvrMenu  w! ;

: setOpen ['] drvrOpen  w! ;
: setPrime['] drvrPrime w! ;
: setCtl['] drvrCtlw! ;
: setStatus ['] drvrStatusw! ;
: setClose['] drvrClose w! ;

: setName { addr len | target -- }
 ['] drvrName -> target
 len target c!
 addr target 1+
 len 31 > if  31 else len then
 cmove
;
 
( write resource to file ) 
: $create-res ( str-addr - errcode )
 call CreateResFile
 call ResError L_ext
;

: $open-res { addr | refNum - refNum or errcode }
 addr call OpenResFile -> refNum
 call ResError L_ext
 ?dup IF ELSE refNum THEN
; 

: close-res ( refNum - errcode )
 call CloseResFile
 call ResError L_ext
;

: make-res { addr len rtype ID name | -- }
 addr len call PtrToHand 
 abort" Could not create resource handle"
 rtype ID name call AddResource
;

: write-out { filename | refnum -- } 
 filename $create-res 
 abort" That resource file already exists"
 filename $open-res
 dup 0< abort" Open resource file failed"
 -> refnum
 refnum call UseResFile
 ['] testDA ['] endDA over - 
 "drvr 12 " Mach 2 DA" make-res
 refnum close-res abort" Could not close resource file"
;

: install-system { | refnum -- }
 " System" $open-res
 dup 0< abort" Open resource file failed"
 -> refnum
 refnum call UseResFile
 "drvr 25 call getresource call rmveresource
 ['] testDA ['] endDA over - 
 "drvr 25 " Mach 2 DA" make-res
 refnum call UpdateResFile
;

: init-DA
( initialize offsets )
 ['] DAOpen ['] testDA -  setOpen 
 ['] DAPrime   ['] testDA -   setPrime
 ['] DACtl     ['] testDA -   setCtl 
 ['] DAStatus  ['] testDA -   setStatus
 ['] DAClose   ['] testDA -   setClose
( initialize driver name )
 " Mach 2 DA" count setname
( initialize driver flags, NeedTime, NeedGoodBye, CtlEnable )
 [ hex ] 3400 setFlags [ decimal ]
( initialize delay time )
 60 setDelay
( initialize event mask, events recommended in IM )
 DAEMask setEMask 
( initialize menu ID, local ID=0 for DRVR ID=12 )
 -16000 setMenuID 
 ( careful! this field will NOT be changed
 by the DA Mover when ID is changed )
;
 
: make-DA
 init-DA
 " Mach2 DA.rsrc" write-out
;

: install-DA init-DA install-system bye ;
{2}
Listing 2: RMaker input
file for the DA example

*   Resources for MACH 2 
desk accessory J. Langowski 1986

Mach2 DA
DFILDMOV

INCLUDE Mach2 DA.rsrc

Type MENU
     ,-16000
My DA
Item 1
Item 2
Item 3
Item 4
(-
Item 6


Type WIND
     ,-16000
Mach2 Desk Accessory
100 131 300 381
Visible GoAway
8
0
 
AAPL
$116.47
Apple Inc.
+0.16
MSFT
$47.98
Microsoft Corpora
-0.72
GOOG
$537.50
Google Inc.
+2.67

MacTech Search:
Community Search:

Software Updates via MacUpdate

Cobook 3.0.7 - Intelligent address book....
Cobook Contacts is an intuitive, engaging address book. Solve the problem of contact management with Cobook Contacts and its simple interface and powerful syncing and integration possibilities.... Read more
StatsBar 1.9 - Monitor system processes...
StatsBar gives you a comprehensive and detailed analysis of the following areas of your Mac: CPU usage Memory usage Disk usage Network and bandwidth usage Battery power and health (MacBooks only)... Read more
Cyberduck 4.6 - FTP and SFTP browser. (F...
Cyberduck is a robust FTP/FTP-TLS/SFTP browser for the Mac whose lack of visual clutter and cleverly intuitive features make it easy to use. Support for external editors and system technologies such... Read more
Maya 2015 - Professional 3D modeling and...
Maya is an award-winning software and powerful, integrated 3D modeling, animation, visual effects, and rendering solution. Because Maya is based on an open architecture, all your work can be scripted... Read more
Evernote 6.0.1 - Create searchable notes...
Evernote allows you to easily capture information in any environment using whatever device or platform you find most convenient, and makes this information accessible and searchable at anytime, from... Read more
calibre 2.11 - Complete e-library manage...
Calibre is a complete e-book library manager. Organize your collection, convert your books to multiple formats, and sync with all of your devices. Let Calibre be your multi-tasking digital... Read more
Herald 5.0.1 - Notification plugin for M...
Note: Versions 2.1.3 (for OS X 10.7), 3.0.6 (for OS X 10.8), and 4.0.8 (for OS X 10.9) are no longer supported by the developer. Herald is a notification plugin for Mail.app, Apple's Mac OS X email... Read more
Firetask 3.7 - Innovative task managemen...
Firetask uniquely combines the advantages of classical priority-and-due-date-based task management with GTD. Stay focused and on top of your commitments - Firetask's "Today" view shows all relevant... Read more
TechTool Pro 7.0.6 - Hard drive and syst...
TechTool Pro is now 7, and this is the most advanced version of the acclaimed Macintosh troubleshooting utility created in its 20-year history. Micromat has redeveloped TechTool Pro 7 to be fully 64... Read more
PhotoDesk 3.0.1 - Instagram client for p...
PhotoDesk lets you view, like, comment, and download Instagram pictures/videos! (NO Uploads! / Image Posting! Instagram forbids that! AND you *need* an *existing* Instagram account). But you can do... Read more

Latest Forum Discussions

See All

Ubisoft Gives Everyone Two New Ways to E...
Ubisoft Gives Everyone Two New Ways to Earn In-Game Stuff for Far Cry 4 Posted by Jessica Fisher on November 21st, 2014 [ permalink ] | Read more »
Golfinity – Tips, Tricks, Strategies, an...
Dig this: Would you like to know what we thought of being an infinite golfer? Check out our Golfinity review! Golfinity offers unlimited ways to test your skills at golf. Here are a few ways to make sure your score doesn’t get too high and your... | Read more »
Dark Hearts, The Sequel to Haunting Meli...
Dark Hearts, The Sequel to Haunting Melissa, is Available Now Posted by Jessica Fisher on November 21st, 2014 [ permalink ] Universal App - Designed for iPhone and iPad | Read more »
Meowza! Toyze Brings Talking Tom to Life...
Meowza! | Read more »
Square Enix Announces New Tactical RPG f...
Square Enix Announces New Tactical RPG for Mobile, Heavenstrike Rivals. Posted by Jessica Fisher on November 21st, 2014 [ permalink ] With their epic stories and gorgeous graphics, | Read more »
Quest for Revenge (Games)
Quest for Revenge 1.0.0 Device: iOS Universal Category: Games Price: $4.99, Version: 1.0.0 (iTunes) Description: The great Kingdom of the west has fallen. The gods ignore the prayers of the desperate. A dark warlord has extinguished... | Read more »
Threadz is a New Writing Adventure for Y...
Threadz is a New Writing Adventure for You and Your Friends Posted by Jessica Fisher on November 21st, 2014 [ permalink ] In the tradition of round-robin storytelling, | Read more »
SteelSeries Stratus XL Hardware Review
Made by: SteelSeries Price: $59.99 Hardware/iOS Integration Rating: 4 out of 5 stars Usability Rating: 4.5 out of 5 stars Reuse Value Rating: 4.25 out of 5 stars Build Quality Rating: 4.5 out of 5 stars Overall Rating: 4.31 out of 5 stars | Read more »
ACDSee (Photography)
ACDSee 1.0.0 Device: iOS iPhone Category: Photography Price: $1.99, Version: 1.0.0 (iTunes) Description: Capture, perfect, and share your photos with ACDSee. The ACDSee iPhone app combines an innovative camera, a powerful photo... | Read more »
ProTube for YouTube (Entertainment)
ProTube for YouTube 2.0.2 Device: iOS Universal Category: Entertainment Price: $1.99, Version: 2.0.2 (iTunes) Description: ProTube is the ultimate, fully featured YouTube app. With it's highly polished design, ProTube offers ad-free... | Read more »

Price Scanner via MacPrices.net

Save up to $400 with Apple refurbished 2014 1...
The Apple Store has restocked Apple Certified Refurbished 2014 15″ Retina MacBook Pros for up to $400 off the cost of new models. An Apple one-year warranty is included with each model, and shipping... Read more
New 13-inch 1.4GHz MacBook Air on sale for $8...
 Adorama has the 2014 13″ 1.4GHz/128GB MacBook Air on sale for $899.99 including free shipping plus NY & NJ tax only. Their price is $100 off MSRP. B&H Photo has the 13″ 1.4GHz/128GB MacBook... Read more
Apple Expected to Reverse Nine-Month Tablet S...
Apple and Samsung combined accounted for 62 percent of the nearly 36 million branded tablets shipped in 3Q 2014, according to early vendor shipment share estimates from market intelligence firm ABI... Read more
Stratos: 30 Percent of US Smartphone Owners t...
Stratos, Inc., creator of the Bluetooth Connected Card Platform, has announced results from its 2014 Holiday Mobile Payments Survey. The consumer survey found that nearly one out of three (30 percent... Read more
2014 1.4GHz Mac mini on sale for $449, save $...
 B&H Photo has lowered their price on the new 1.4GHz Mac mini to $449.99 including free shipping plus NY tax only. Their price is $50 off MSRP, and it’s the lowest price available for this new... Read more
Check Apple prices on any device with the iTr...
MacPrices is proud to offer readers a free iOS app (iPhones, iPads, & iPod touch) and Android app (Google Play and Amazon App Store) called iTracx, which allows you to glance at today’s lowest... Read more
64GB iPod touch on sale for $249, save $50
Best Buy has the 64GB iPod touch on sale for $249 on their online store for a limited time. Their price is $50 off MSRP. Choose free shipping or free local store pickup (if available). Sale price for... Read more
15″ 2.2GHz Retina MacBook Pro on sale for $17...
 B&H Photo has the 2014 15″ 2.2GHz Retina MacBook Pro on sale for $1799.99 for a limited time. Shipping is free, and B&H charges NY sales tax only. B&H will also include free copies of... Read more
New Logitech AnyAngle Case/Stand Brings Flexi...
Logitec has announced the newest addition to its suite of tablet products — the Logitech AnyAngle. A protective case with an any-angle stand for iPad Air 2 and all iPad mini models, AnyAngle is the... Read more
Notebook PC Shipments Rise Year-Over-Year as...
According to preliminary results from the upcoming DisplaySearch Quarterly Mobile PC Shipment and Forecast Report, the global notebook PC market grew 10 percent year-over-year in Q3’14 to 49.4... Read more

Jobs Board

*Apple* Solutions Consultant (ASC)- Retail S...
**Job Summary** The ASC is an Apple employee who serves as an Apple brand ambassador and influencer in a Reseller's store. The ASC's role is to grow Apple Read more
Project Manager, *Apple* Financial Services...
**Job Summary** Apple Financial Services (AFS) offers consumers, businesses and educational institutions ways to finance Apple purchases. We work with national and Read more
*Apple* Store Leader Program - College Gradu...
Job Description: Job Summary As an Apple Store Leader Program agent, you can continue your education as you major in the art of leadership at the Apple Store. You'll Read more
*Apple* Retail - Multiple Positions (US) - A...
Sales Specialist - Retail Customer Service and Sales Transform Apple Store visitors into loyal Apple customers. When customers enter the store, you're also the Read more
Senior Event Manager, *Apple* Retail Market...
…This senior level position is responsible for leading and imagining the Apple Retail Team's global event strategy. Delivering an overarching brand story; in-store, Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.