0xACE

It is based on the testing branch and shows no merge conflicts with that branch at the moment. I will have to think about you other GUI questions. I'm not sure what the best approach would be for the GUI. But, yes, merging the development would be best. Mid-september is fine. I'm in no rush.

Thank you. Yes you can manually enter the local delays in the GUI. In the textbox where the macro gets recorded. My only idea on recording the delay was to track the time between keystrokes when recording. I've not developed in Qt so the GUI is foreign to me at the moment. Also, I have not adapted the GUI for setting the global delay to a value either. I did make the globe delay value accept 'on' so that it would be compatible with the current GUI.

Using the great work done on by MSC, Frickler, and others I have created a fork (and a pull request) of the testing branch that allows for key-by-key delay in macro playback as well as a global delay. https://github.com/stephenhouser/ckb/tree/macro-delay Here is an excerpt from the DAEMON.md documentation: ----------------------- Macro playback delay There are two types of playback delay that can be set with macros; global and local. Setting a global delay value introduces a time delay between events during macro execution or playback. Local delay allows setting the delay after an individual event, overriding the global delay value for that event. Thus global delay can be used to set the overall playback speed of macros and local delays can be used to tune individual events within a macro. All delay values are specified in microseconds (us) and are positive values from 0 to UINT_MAX - 1. This means delays range from 0 to just over 1 hour (4,294,967,294us, 4,294 seconds, 71 minutes, or 1.19 hours). A value of zero (0) represents no delay between actions. Global macro delay (default delay) Global delay allows macro playback speed to be changed. It sets the time between (actually after) each recorded macro event. If global delay is set to 1 microsecond then a 1 ms delay will follow each individual macro event when the macro is triggered. The global delay is set with the ckb-daemon's existing (in testing branch) delay command followed by an unsigned integer representing the number of microseconds to wait after each macro action and before the next. Global delay can also be set to on which maintains backwards compatibility with the current development of ckb-daemon for long macro playback. That is, setting the global delay to on introduces a 30us and a 100us delay based on the macro's length during playback. NOTE: This setting also introduces a delay after the last macro action. This functionality exists in the current testing branch and was left as-is. It is still to be determined if this is a bug or a feature. Examples: delay 1000 sets a 1,000us delay between action playback. delay on sets long macro delay; 30us for actions between 20 and 200, 100us for actions > 200. delay off sets no delay (same as 0). delay 0 sets no delay (same as off). delay spearmint-potato is invalid input, sets no delay (same as off). Local macro delay (keystroke delay) Local Delay allows each macro action to have a post-action delay associated with it. This allows a macro to vary it's playback speed for each event. If no local delay is specified for a macro action, then the global delay (above) is used. All delay values are in microsecods (us) as with the global delay setting. Examples: macro g5:+d,-d,+e=5000,-e,+l,-l=10000,+a,-a,+y,-y=1000000,+enter,-enter define a macro for g5 with a 5,000us delay between the e down and e up actions. A 1,000us delay between l up and a down, a delay of one second (1,000,000us) after y up and before enter, and the global delay for all other actions. macro g5:+d,-d=0 use default delay between d down and d up and no delay (0us) after d up. This removes the noted feature/bug (above) where the last action has a trailing delay associated with it.