Quote Originally Posted by Bettysue View Post
Code:
<Label Joe local SendWin WoW1>

<KeyList TTL 1-9>

<Template PFTL>
<hotkey %1%>
<Toggle>
<SendFocusWin>
<Key %2%>
<Wait 500>
<SetToggle 1 Hotkey %Trigger%>
<Toggle>
<SendFocusWin>
<Key %Trigger%>
<Cancel>
<EndTemplate>

<ApplyTemplate PFTL TTL B>

<MovementHotKey Left, Right, Up, Down>
<SendLabel Joe>
<Key %Trigger%>
Using the above code i am able to get the rapid alternating b1b1b1b2b2b2b2b3 etc, while moving without issue. It has a 500ms timeout and will always start with the assist key first after the timeout.
This should get you closer, if it doesn't work for you let me know what's happening, I'll try to work something out.
I just wrote the template to quickly make the number row work that way...
I have my movement keys set up differently, so that wouldn't work. Also, I'm a bit averse to <wait> commands because of the lock-up and eula-stuff. It's not just the movement keys, it's also stuff like my /stopcasting macro etc. When spamming a <wait> command, nasty things will happen - believe me :-) I tend to keyspam really hard and I don't like my stuff to lock up.

Also, it's probably not a problem in practice, but I wan't to stay on the safe side of the EULA. Basically I see the "<wait>" method as a work-around with more disadvantages than advantages. If I'm going to play in the grey-area of the EULA, I might as well just have two keypresses in one hotkey (which is what /click macros do anyway), but I'm staying away from that for now :-)