Quote Originally Posted by Spunktank View Post
Any ideas would be much appreciated.
I would try and support the other tools where they are weak versus making a new multiplexer. If the multiplexers were open a bit with the net protocol you could feed to them or if they were hookable you could do the same.

Anyways, what I have been toying with:

* Button mash throttle, reduce same repeated keys on a key by key basis. So if you spaz out and hit backspace for your 'all nuke key 3 times per second, it will 'absorb' 2 of them if your throttle was at 1 per second.

* Log key events to hires timestamp log (timestamp, keybind, keyevent, flag/comment) for crazy people to look at with a separate tool. Flags might be throttled to dev null, keystroke underbuffered, etc.

* Load /wtf/account/${acct}/bindings-cache.wtf into the tool for planning your maps (you want to map 'G' to something in your Windows tool, the tool will already tell you that G is target previous noob, shift-B is OpenAllBags, etc. Useful for planning keys. Pick a addon like BindPad and allow some further planning such as "bind ALT-G CLICK BindPadMacro:gnf" and possibly laying that out a bit.

* Detect end user lag to a degree to smartly tell the user they are boned for video or similar. So the time it takes to shuffle a window and the cpu spike occurs (see above log). So comment 'max cpu' or 'disk trash' or 'virtual memory cap hit'

So a multiplexer and a service that monitors the system a bit as well as the multiplexer and its targets.

EDIT: And reads mail and does twitter.