Cliclick Version History
- Added support for numpad keys when using the “keypress” (
- Support reading commands from stdin (use
-[a dash] as filename with
- Change donation switch from
-nto avoid ambiguity
- Fix handling of absolute negative coordinates
- Added color picker (“cp”) action: can be used to read the RGB color values at a specific screen coordinate. Example: “cliclick cp:123,456”
- “Keypress” (“kp”) action now supports the Enter key
- Improves reliability of doubleclicking on some systems
- Fixes crashes with non-Western keyboard layouts
- Fixes potential crashes when arguments are formally invalid
- Other minor improvements
- Bugfix: For the “keypress” (“kp”) command, fixed keys “volume-down”, “volume-up” and “mute”.
- Bugfix: Typing did not work in “verbose” mode
- Change: For the “keypress” (“kp”) command, removed support for “help” key, which didn’t work anyway.
- New: “keypress” (“kp”) command supports additional keys: “brightness-up”, “brightness-down”, “play-pause”, “play-previous”, “play-next”, “keys-light-toggle”, “keys-light-up”, “keys-light-down”
- Improves reliability of “drag & drop” operations and reduces the need to add “wait” commands for dragging to work correctly.
- Fixed a few bugs related to memory management
- Fixed a command-parsing bug that occurred when typing text containing a colon
- Added support for a few diacritical characters on the US Extended keyboard layout
Implemented the most requested feature: typing (almost any) arbitrary text using cliclick. Example:
cliclick t:'Wow, it works!'
- Added support for dragging using commands dd (“drag down”) and du (“drag up”). Code contributed by J. Lewis Muir.
- Fix: When using “key down”, “key up” or “key press” with more than one key, the events were often fired too fast, resulting in only the last key being recognized by the OS.
- Added several new keys that can be used with the “keypress” (“kp”) command.
- Added several new keys that can be used with the “key down” (“kd”) and “key up” (“ku”) commands.
- Relative coordinates: Whenever a command expects a pair of coordinates, you may provide relative values by prefixing the number with + or -. For example, “m:+50,+0” will move the mouse 50 pixels to the right. Of course, relative and absolute values can be mixed, and negative values are possible, so “c:100,-20” would be perfectly valid. If you need to specify absolute negative values (in case you have a setup with a second display arranged to the left of your main display), prefix the number with =, for instance “c:100,=-200”.
- cliclick has been released as Open Source software. The repository can be found at https://github.com/BlueM/cliclick
- New command: “kp:<key>”, which stands for “key press” and which means a “key down” plus a “key up” event. Other than “kd” and “ku”, which are intended for modifier keys, “kp” is for emulating “regular” keys that do not have to be held down while performing other events. Currently “return” and “esc” are supported as key, which can be handy for confirming or canceling dialogs.
- Added command-line option “-w” for specifying a default pause (in milliseconds) after each event. This can be used in addition to the wait command and/or may be used to reduce the number of wait commands you need.
- Added command-line option “-f” for reading commands from a file. Each line in the file is expected to contain a command in the same format/syntax as the commands given as arguments at the shell (for instance: “c:200,300”). Additionally, lines starting with the hash character “#” are regarded as comments, i.e.: ignored. Leading and trailing whitespace is ignored, too.
- New syntax: more readable, more flexible, more consistent and more open to future additions
- Added support for triple-clicking
- Added support for “alt” modifier key
- Added support for moving the mouse without clicking
- Added testing mode, which will not perform any actions, but instead print a description of what would have been done to STDOUT
- Added a means to print arbitrary messages (primarily for debugging purposes) and to print the current mouse location as part of a sequence of clicks/events
- Code uses a newer API
- Fixed “m” for getting the mouse’s current y location (in 1.3, always returned 0).
- Added “-r” switch to restore mouse location to the initial position
- Added switch “-q” to simply print the current mouse location
- Instead of a number, you may pass “m” as x and / or value to use the current x and / or y position.
- Added support for doubleclicking and control-clicking (contextual menu clicks)
- Added support for a series of consecutive clicks
- Initial release