SamyGO

zoelechat wrote:

sectroyer wrote:The only question that remains is that whether I should add "&" by default

In my opinion it's better to let user choose as it is now. We can imagine cases where queuing is needed and I wonder what could be the side effects of massive multiple simultaneous injections if script doesn't check itself to be already running

The fact now is that when you run a command that takes longer period of times you are hanging up (of course one thread) exeDSP. As a result it may even cause crash

Do you mean that if, for example, I insert ~"sleep 60" in my script launched (at least) twice in foreground it will cause crash? I'm going to try...
So, we have the choice between mandatory '&' and potential simultaneous injections which may also cause crash (?)
Anyway it's up to you, you're the sole master

edit: result here is no crash during "sleep 60", just hanging (rc doesn't respond) until script finishes and execute again, but I take back hand at the end

That's what I told. Running script in the background by default shouldn't have any negative implications:)

If user is aware that script needs self check to prevent simultaneous launches you're right

I will think about all of this in the future. Now just be happy:)

No complaint at all, I am happy with this best improvment for a long time...
Even if you "simplify" it for public, I prefer current version which offer more opportunities

proper way would be to create a thread

Yeah. I need to check whether it will work correctly across all platforms:)

New version uploaded. Creates thread for every new command No more crashes Please test

If I understand correctly I can remove '&' and script self-test if I want script to be executed once (even with long key press)?