Simple Macro Recorder

[Kum Filteau]

SimpleMacro Recorder allows you to record a sequence of events to create a Windows macro. The Macro Recorder will record keystrokes, mouse events and window activations, including window positions and dimensions. This makes it easy to create a macro that can be played back to run the task automatically.

The Macro Recorder is also available in all editions of Macro Scheduler, including Macro Scheduler Lite our affordable entry level automation tool.The Macro Recorder creates real MacroScript code that is easy to understand (and edit in Macro Scheduler).When recording a macro you can specify an application to automate so that the Macro Recorder can add the code to open the application andposition it in the same place on the screen each time so that your macro will always work correctly.

When you record a macro you can specify the playback speed and mouse sensitivity.Adjusting the playback speed effectively reduces or lengthens the time between individual steps.It is usually best to leave this in real time as reducing time between events can in some instances make the macro less reliable - the systemneeds the thinking time between those events. Reducing mouse sensitivity means you can remove unnecessary mouse moves between mouse clicks,for example, thus shortening the script and making it easier to read and edit.

The Macro Recorder is ideally suited to less technical users, or those new to Macro Scheduler who want to learn the MacroScript language to make their macros morepowerful and more reliable in changing environments. The Macro Recorder in combination with the optional script compiler in Macro Scheduler Pro allows a user to create a standaloneWindows application that will run on any PC to automate repetitive tasks in just a few simple mouse clicks.

Simple Macro Recorder offers only a tiny fraction of what is available in our flagship Automation Solution Macro Scheduler.So if you need more powerDownload a FREE 30 Day Trial of Macro Scheduler, or Buy Macro Scheduler today.

When you record a macro, the macro recorder records all the steps in Visual Basic for Applications (VBA) code. These steps can include typing text or numbers, clicking cells or commands on the ribbon or on menus, formatting cells, rows, or columns, or even importing data from an external source, say, Microsoft Access. Visual Basic Application (VBA) is a subset of the powerful Visual Basic programming language, and is included with most Office applications. Although VBA gives you the ability to automate processes within and between Office applications, it is not necessary to know VBA code or computer programming if the Macro Recorder does what you want.

It is important to know that you when you record a macro, the Macro Recorder captures almost every move you make. So if you make a mistake in your sequence, for example, clicking a button that you did not intend to click, the Macro Recorder will record it. The resolution is to re-record the entire sequence, or modify the VBA code itself. This is why whenever you record something, it's best to record a process with which you're highly familiar. The more smoothly you record a sequence, the more efficiently the macro will run when you play it back.

When you record a macro for performing a set of tasks in a range in Excel, the macro will only run on the cells within the range. So if you added an extra row to the range, the macro will not run the process on the new row, but only the cells within the range.

It is not necessary that only tasks in Excel can be recorded in a macro. Your macro process can extend to other Office applications, and any other applications that support Visual Basic Application (VBA). For example, you can record a macro where you first update a table in Excel and then open Outlook to email the table to an email address.

To assign a keyboard shortcut to run the macro, in the Shortcut key box, type any letter (both uppercase or lowercase will work) that you want to use. It is best to use Ctrl + Shift (uppercase) key combinations, because the macro shortcut key will override any equivalent default Excel shortcut key while the workbook that contains the macro is open. For instance, if you use Ctrl+Z (Undo), you will lose the ability to Undo in that Excel instance.

Although the description field is optional, it is recommended you enter one. Also, try to enter a meaningful description with any information that may be useful to you or other users who will be running the macro. If you create a lot of macros, the description can help you quickly identify which macro does what, otherwise you might have to guess.

You can work with recorded code in the Visual Basic Editor (VBE) and add your own variables, control structures, and other code that the Macro Recorder cannot record. Since the macro recorder captures almost every step you take while recording, you can also clean up any unnecessary recorded code that serves no purpose in the macro. Reviewing your recorded code is a great way to learn or sharpen your VBA programming skills.

When you record a macro for performing a set of tasks in a range in Excel, the macro will only run on the cells within the range. So if you added an extra row to the range, the macro will not run the process on the new row, but only the cells within the original range.

To assign a keyboard shortcut to run the macro, in the Shortcut key box, type any letter (both uppercase or lowercase will work) that you want to use. It is best to use key combinations that don't correspond to existing shortcut keys, as a macro shortcut key will override any equivalent default Excel shortcut key while the workbook that contains the macro is open.

Although the description field is optional, it is recommended you enter one. It's helpful to enter a meaningful description with any information that may be useful to you or other users who will be running the macro. If you create a lot of macros, the description can help you quickly identify which macro does what, otherwise you might have to guess.

Are there any plans to equip Gimp with macro recorder? I mean kind of toolpresent, for example, in LightRoom, where every change applied to picture islisted on the screen - and one can then copy a whole "procedure" with simple- then apply that series of commands by - onto anyother picture, not being forced to start whole procedure all over again.

And such recorded list of procedures/commands - and I mean literally everyprocedure listed in GIMP's menus, be it internal command or installed script- it should be possible to save it into ordinary text file, and then to useit as a parameter in case of batch processing, I mean something like this(parameters fictional, just example how do I see this):

Something like this should apply recorded actions - one after another - toeach *.jpg file found in current directory. I mean batch processing usingGIMP in ImageMagick's way. Correcting only one picture - while recordingactions during the process - then applying sequence of actions to whole setof next pictures, using GIMP as command-line tool.

GIMP has long history - but if I'm correct it still doesn't have suchability until this day. Yes, I found some tools like BIMP, I found the tips"learn Script-Fu language" - but actually why until now such obvious thingrequires learning special programming language? GIMP "knows" what have Idone while processing picture, so it should be able to list my actions likethis:

GEGL - was started to revamp GIMP with a new enginethat can handle floating point raster images, as well as enable thingslike non-destructive editing, which is what you are describing.Non-destructive editing is the next thing on GIMPs roadmap, now afterporting core to rely on GEGL apis, and the current cycle of portingfrom GTK2 to GTK3 is done. Non-destructive editing seem similar toscripting and macro recording and the existing GIMP framework forexposing actions for scripting languages. But actual non-destructiveimage editing belongs in the layer stack together with layer modeoperations. The work on porting the functionality of gimp-2.6/2.8 toGEGL is quite complete with 2.10, but the only real feature GIMP hasgained/exposed is working at higher bit-depth. There is another wrongdirection some people are taking when considering action recorders forGIMP, the undo stack - but due to how it works in GIMP that is alsonot a fruit-ful way to do it.

3a8082e126