'Run continuously' action not running continuously

[cmdr.m...@gmail.com]

I have an 'event loop' action set up to start when a profile is loaded and to run continuously.  However it commonly stops without starting again, and when it does the log window shows that the action stops but doesn't show it starting again.  I'm unsure as to why it stops sometimes, but it might be after the profile has been edited.

How can I ensure that the action does restart when it stops?

[Luca D]

Did you check the option to stop when the active window loses focus?
It's usually ON by default...

[cmdr.m...@gmail.com]

It's not checked, no.

[Gary]

This is something I would need to look into, since editing or changing profiles stops all commands.  I can see editing not stopping an active command (as long as the command being edited is not the one that is running).  Then again, the idea is to stop input commands from affecting what you are doing, which may not be desirable for most, and I'd hesitate adding an option to allow it.

Changing profiles is another story, as that could break as subcommands could possibly not be resident at the time of execution.

Gary

[cmdr.m...@gmail.com]

Would it be possible to restart any "run this on profile load" commands if present after editing is done?

[Gary]

Something to consider...

Gary

[cmdr.m...@gmail.com]

This is turning out to be a real problem issue for my plugin, because it relies on a particular command running all the time and it's being turned off at various times (usually after editing a profile but it does seem to happen at other times as well).  I've been thinking about this and realise that restarting the "run this on profile load" could be detrimental (if the command has initialisation-type stuff in it) but if a command has 'run continuously' checked it seems fair to restart the command whenever it is stopped.  Would you agree?  

[cmdr.m...@gmail.com]

Any further thoughts on this?

[cmdr.m...@gmail.com]

Sorry to keep bumping this, but it continues to be the #1 issue for users of my plugin.

As below, if a command has 'run continuously' checked can it be restarted whenever it is stopped for any reason?

[Gary]

I can look into adding an option to run the profile startup command after edit, if that would suffice.  I can add a new execution type that can be checked with the {CMDACTION} token so you can differentiate between an edit exec and a startup exec.

I looked into allowing things to keep running when the profile is being edited and found that there's way too much that could go wrong if things kept going in the background o_O

Gary

[cmdr.m...@gmail.com]

It's a solution, although not really optimal as it means scattering the logic across multiple commands.

Note that I'm not after keeping commands running when the profile is being edited, just restarting those marked for continuous running once the editing is complete.  Is this not a possible solution?

[Gary]

I thought you said there was a command that was run when the profile was loaded?  The logic can be put in that same command.  Outside of that, I'm not sure what I can do for this.

Gary