[v1.7.0.4] "Get User Input" dialogs unresponsive to "Stop running commands"

[Pfeil]

This isn't a bug, but stopping commands while a "Get User Input" dialog is open(which cannot be done using the main window button as that is disabled while the dialog is open, as an aside) will show "Stop running commands" in the log, while the dialog will remain open(other running commands do stop).
Only when the dialog is closed will the command stop(with an appropriate log message).

I feel it makes sense to have the dialog close when the command is stopped(either specifically or when all commands are stopped), as the input will likely not be processed(unless the variable is used by a plugin still running in the background) despite it modifying the variable assigned to it when the dialog is closed by the user.


EDIT: Fixed somewhere along the line, checked in v1.7.2.21

[Gary]

The, 'Get User Input' screens will now close when, 'Stop All Commands' is issued, as well as a, 'Kill Command' action, and  the variable will not be altered.

On a side note, the, 'Kill Command' screen did not have a, 'Kill by Name'.  There was code to support it, but it was not exposed through the UI.  I wonder if that was intentional o_O...?  Anyways, that's in there now, too.