Quick Macros
What is Quick Macros?
Quick Macros automates repetitive tasks, even the most complex. Your macros can press keys, click buttons, links, menu items, on-screen images and other UI objects, manage windows, run and manage files, wait for various events, show dialogs, send/receive internet files and email, automate web pages, get/set text of UI objects, process text/HTML/XML/CSV, automate Excel, use databases, and many more. Creating macros is easier with the mouse/kayboard recorder, tool dialogs, tools to capture various objects and images, intellisense, dialog editor, debugger. To run macros you can use hotkeys, autotext, mouse, window, schedule and other triggers, create pop-up menus and toolbars. Quick Macros can add your toolbars to any window, auto-close annoying popup windows, auto-complete or correct text as you type, remap keys, convert your macros to independent .EXE programs, run from a USB drive. More functions can be created with the QM programming language that supports user-defined types, classes, COM, DLL functions, embedded VBScript/C#/VB.NET/C scripts, and everything for programming even at Windows API level.
Quick Macros Screenshots
Quick Macros Features
Quick Macros information
Supported Languages
- English
Comments and Reviews
Tags
- Automation
- toolbars
- automated-tasks
Category
Office & ProductivityList containing Quick Macros
Windows UtilitiesRecent user activities on Quick Macros
sevencats added Task Automation as a feature to Quick Macros
sevencats added Quick Macros as alternative(s) to LibreAutomate C#- altts1zed added Quick Macros as alternative(s) to Anacron
It is elaborate, convenient and very thorough. I did not perceive Quick Macros that way before I started using it. I used AutoHotkey and, occasionally, AutoIt. I had 1 main (745 lines of code) AutoHotkey script + 42 smaller helper scripts and thought Quick Macros would not be any better.
I bought Quick Macros just to have new experience. My main AutoHotkey script is still running (because there is a lot to rework), but I automated much more tasks with Quick Macros in a shorter period of time than I was able with those 42 smaller helper AutoHotkey scripts.
The pivot points are the GUI that helps to record and manage all macros in one place and the fact that Quick Macros runs all macros in one server process that consumes only ~5Mb of memory. With AutoHotkey I was running each script separately and ~8 of them were #persistent which resulted in 8 AutoHotkey.exe processes running constantly (~5Mb each). I remember in one AutoHotkey script I was not able to send Ctrl+S reliably to an application and Quick Macros does this flawlessly.
Quick Macros has great help file that describes a lot of functions with examples, so that (to that point) I have automated everything I wanted. A couple of times I visited Quick Macros forums to add functionality that is not yet in standard setup (clipboard triggers and TcpIpClient).
I use it daily.