Changing port or polling interval doesn't take effect if rcmd is already enabled #198
Assignees
Labels
Comments
csatt
added a commit
that referenced
this issue
Apr 5, 2023
Modified the rcmd_apply() method to handle the case where remote commands are already enabled, and the user changes the port number and/or the polling interval. Previously, such a change would not take effect when the user clicked OK. They would only take effect if the GUI was closed or if the user disabled and then re-enabled remote commands. Now, in this case, the remote command monitor is canceled and restarted with the new port and/or interval.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If remote command monitoring is already enabled, and the user changes either the port number or the polling interval, the change does not take effect unless the user first disables remote commands (and clicks OK), or kills the app (or instance.) The change should take effect immediately when the user clicks OK. This implies that the currently running remote command monitor needs to be stopped before restarting it with the new value(s).
The text was updated successfully, but these errors were encountered: