Can't get delay to work in command

[phil]

Not wrong per say, just not something I had considered... And when XMBC changes layers, it aborts running simkeys (all of them, no questions asked) - and that's the problem here... its aborting it before it has finished!

The question to me is can I just change that so it does not abort, or will that cause more harm than good. In previous versions, it could only run one simkey sequence at a time (no matter which button etc.) that's changed in 2.21 beta where it can run one per button at a time.

But that still leaves the problem, when layers change should it abort anything already sent or not. If its a repeating, sticky or during (method3) simkey, I think it needs to stop it (as the layer goes away, it looses context and the repeat should no longer be repeating, as the layer is no longer active. But I don't think it needs to abort non-repeating/button held down simkeys as they have already been sent, the layer going away does not have any impact on them, do why should it abort them! Sounds sensible in theory - but I need to re-study the code to make sure I'm not missing anything.

It does beg the question, if you had setup the simkey for "on button released" (method 2) and the layer changes before the button is released, what should it do (I guess nothing because the button will be released on a different layer, thus not the same action!)... I think thats OK (as in that will be what it does currently anyway. Its only going to be an issue for method 1 (and possibly method 9 but that's probably safer to leave as is too).

[magnumforce2006]

Ok, well if you'd like me to try some settings or something to help in testing let me know.

[phil]

I don't think there is anything to try - at least, not before I make some changes...
Once I do make some changes, I'll let you know and you can give that a try!

[magnumforce2006]

Sounds good!

[phil]

OK give 2.21 Beta 49 a try - I just built it and I hope it will fix it.

It should work, but one thing to note, since your layer key is CTRL+SHIFT, that means any keys sent (while the layer modifier key is still held down) will also have ctrl and shift applied. This probable wont matter seeing as all your foobar hotkeys keys also include ctrl+shift (+alt), but you can actually circumvent this if you wanted to by putting {release}{ctrl}{release}{shift} at the beginning.

That would virtually release the keys (it wont release the layer until you physically release the keys, but it will prevent them from interfering with the rest of the macro.

You probably don't need to worry about that in this case, but just to make you aware .

If it does not work, another debug log would be useful!

[magnumforce2006]

Updated, re-ran. It works! Thank you!

[phil]

Perfect - that's what I like to hear