I am happy to publish links to your *.REC files at this site. Please e-mail me with the details once you've read my guidelines below. (While numbers remain low I may even be able to find the space to hold them on my own site.
As recorder files often only work well on the system on which they were created I encourage you to send me a copy of any macro files you wish me to publicise. It will help me learn more about how others use RECORDER, and give you a chance to have your macro tested on yet another system!
I do not plan to make available or publish links to any macros which include any mouse movement records.
In Recorder mouse movements are recorded in terms of the number of pixels covered. Because of the huge range of possible screen resolutions and window sizes on which a macro might be played back, I do not believe it is practical to publish such macros. Macros which include mouse movement, clicks and drags, should be thought of as for your machine only.
I believe it is best to include all documentation about running macros within a *.REC file itself rather than in a separate file. That way you can ensure that current documentation and macros do not get separated! This can be done easily in Recorder by using the "Description" box within the "Macro Properties" dialogue.
Prepare your description in NOTEPAD, or similar, and paste it into the Description box. In this way you use carriage returns to create multi-paragraph descriptions and use tabs (RECORDER will set all tabs at fixed 8 characters stop positions) if you so wish.
The description of each macro should include details of:
In most cases it should not be necessary to give detailed descriptions of the key strokes used. A user can reveal the details of the time every key was struck and released when the macro was recorded by shift-clicking Properties (or using shift-p) on the Macro menu of Recorder.
You should consider creating an initial macro which will copy the macro name and contents of its details box of all the macros in the file into a Write or Notepad file. This can make it easy for the user to read and, if necessary, print out the full documentation. (One way of achieving this is to create a base file with just this macro in it and then merging your working macros with it before making them available for download.)
[ Top of Page ]