Sat Jul 09, 2011 11:30 am by mo_ron
Your 'hack' was perfect. Thanks!
I was able to verify that it is doing what I thought it was doing. Not sure if this is meant to work this way or this is a bug:
2 mapped keys. The first we'll call 'Skill'. It has two steps. The first step would send a keystroke to a client to execute a skill. The second step would be empty but would be marked as "Do not advance to next step for at least 1 second".
The second mapped key is bound to a key which I will call from my main client. It has one step. The step calls the mapped key 'Skill' twice with each keypress.
The goal of this was to slow down skill rotations by class. (lotro). Some classes have inductions. Some don't. Depending what class I'm playing as my main, the main skill rotations have different speeds so I wanted different speeds for the other clients depending on what class I was using for my main.
When I press the second mapped key it correctly executes the keystroke in the first step of the 'Skill' mapped key. It also executes the second step and gets stuck there until the one second has elapsed. So far so good. Now, if I wait 5 seconds (more than enough time for the 1 second delay to expire) and I press my second mapped key, it executes the 2nd step of the 'Skill' mapped key twice. If I press it again, it has now advanced back to the first step and steps 1 and 2 both execute.
I was expecting it to execute the 2nd step once. It would see that the delay is complete and then advance to the first step which would also be executed because of my second call to the 'Skill' key map from the same keypress. Am I not understanding something?