You can't stop a BC when it has been "nested" That is why it can be a little better to keep it expanded.
I think something must be wrong, because typing in delay times should be really easy. Touch the delay button, type in the numbers. Thats it..
I do notice crashes very rarely when trying to program over a key command. I find it better to instead add a new "Key Command" line, then type in what you need, and remove the previously line if that is what you need to overwrite.
Jamey Z Slate Media Technology Jamey@stevenslate.com
Post by audioinsight on Aug 20, 2015 23:15:53 GMT -8
So after using one of my new macros alot- I can confirm that you can stop a nested event- you just need to wait until the stop appears very briefly / randomly.
No its not better to keep it expanded- because as the topic of this discussion says- you want to repeat a bunch of commands x amount of times- there is no other way to do it. Saying that its better to keep it expanded- is ridiculous. When would you ever actually want just the same 1 key repeated?? Please re-think your attitude towards this. Make it simpler & more standard to allow this. Once its in user- it should behave the same as any other command from post, music, etc. Thats the only way it should work. Get over this nonsense of thinking expanded is better- its not. Common streamlined functionality- over convoluted different behaviour from the same things in different columns.
Regarding delay & repeat time- yes something is wrong with BC. It does it on my other Yosemite partition too. Please fix it. Trust me, I have tried every way of clicking on the delay "button" with my mouse. Needs more standard manual plugin value input type behaviour. Its really sticky at the mo- pretty unusable. Its not me or my system.
My crashes when programming macros- happen on a multitude of things- even hitting add keystroke. Have done it either & both ways changing a command. Crashes seem more time related- its the longer I spend in the program window- the more likely it will just crash. Ive had it crash having left it for a while not doing anything with program window open. Thankfully it seems to not crash once programmed. Definitely needs debugging- the code is not stable. Please stop deflecting the issues here as if its my user error. Just fix the code and lets all move on happier.