Note Input State bugs/Issues

I am using Windows 10 (Musescore 3.6.2 and the latest nightly build) and have found the following bugs in interactions with plugins and the UI Note Input state:

1) Running the "Hello World" plugin (installed with Musescore) from Plugin Creator will cause Musescore to crash (evaporate) if the user interface is in Note Input state . In fact, running any plugin from the Plugin Creator will cause Musescore to crash (evaporate) if the UI is in a Note Input state. There is normally a few/several seconds delay after executing the plugin before Musescore crashes.

But if you are quick at clicking on the main musescore UI you can prevent the crash.

2) If a plugin that contains the executable line (and the UI is not currently in a Note Input state):

cmd("note-input") //This should put the UI in a Note Input state

it will cause Musescore to crash (evaporate). The crash occurs whether the plugin is run form the Plugin Creator or from the UI. There is normally a few/several seconds delay after executing the plugin before Musescore crashes.

However if you duplicate the note input command, i.e. have code like:

cmd("note-input")
cmd("note-input")

Everything works OK (except you don't get to put the UI in a Note Input state!). Presumably the second instance of the command takes Musescore out of an unstable state before it can crash.

3) If Musescore is put in a Note Input state, and you open (or have open) the Plugin Creator and have a plugin displayed and you click on the text editor part of the Plugin Creator and then click on the main UI it will cause Musescore to crash.