Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
Autorepeat delays in single place
Autorepeat delays in single place
I wonder if it would be possible to configure the autorepeat delays in one central place, so if I adjust the delays it would affect all the different macros? I guess I could make my own autorepeat plugin with hard coded delays, but I'd prefer using the original.
Re: Autorepeat delays in single place
There's no ability to do so currently, but it would certainly be nice if EVERY action could preserve a set of user-selected defaults. I leverage a custom module, for example, to fire OSD notifications so I can tweak their styling in one centralized location rather than going through and updating each and every macro by hand when I want to change something, which is a clumsy solution at best. If defaults could be set and all actions had a "Use defaults" checkbox, this sort of hack wouldn't be necessary.
There are at least a few caveats that would need to be addressed (such as how to designate which options can and can't be saved as a default -- we might want our programs to be launched in a maximized window by default, for example, but if all options in the window were saved, the executable path and command-line parameters would render defaults for the Start Application action worthless), but conceivably, this is something that, if properly engineered, could be accomplished without a tremendous amount of work. I won't be taking it on myself (no, for real this time), but a man can dream, right?
There are at least a few caveats that would need to be addressed (such as how to designate which options can and can't be saved as a default -- we might want our programs to be launched in a maximized window by default, for example, but if all options in the window were saved, the executable path and command-line parameters would render defaults for the Start Application action worthless), but conceivably, this is something that, if properly engineered, could be accomplished without a tremendous amount of work. I won't be taking it on myself (no, for real this time), but a man can dream, right?
/bw