Allow com port exclusion

[VonSzarvas]

Computer with bluetooth ports (or even worse multiple bluetooth, such as audio bluetooth devices) take a VERY long time to start the download. (> several seconds). Solved when bluetooth ports disabled in Windows Device Manager- although then we lose audio for Hangouts whilst working in BlocklyProp.

Might be an issue with other port types I do not have.

New feature would be good to allow user-selectable com ports to be ignored,
and/or tickbox to auto-ignore bluetooth ports
and/or tickbox for Solo to "only look at selected com port"

Without giving all scenarios great thought, that last option might be simplest. Or perhaps a combination of the last two options, if there is no such thing as a bluetooth serial com port device.

[PropGit]

This may be something that is handled completely by Launcher (rather than Solo or Solo+Launcher), depending on how implemented.

Bluetooth ports have been a problem like this for > a decade. Launcher automatically ignores bluetooth ports already, at least the ones that match the non-case-sensitive ' bt ' (note the spaces) or 'bluetooth' anywhere in the port friendly name (the text string that appears in Device Manager associated with the COM#).

Perhaps you have one that doesn't match? Please share your bluetooth port names (strings).

Launcher isn't opening any of the ports until instructed to do so; a Bluetooth port should not be causing this lag during download... it only opens the port that the user selected. The delay you're describing is certainly of concern to me for this reason as well.

[zfi]

@VonSzarvas Solo relies on Launcher for port enumeration. Solo does maintain a list of ports as reported by Launcher but it is only used for those times where Solo and Launcher are taking more than a couple of seconds to sync up after a disconnect. Managing the available ports in UserLand is not a trivial exercise. Let's isolate the issue you are experiencing and then re-examine the need for further port management.

[PropGit]

@VonSzarvas @zfi That gives me an idea... the delay may be due to an unexpected Solo+Launcher disconnect. Try opening the Launcher log view, and/or Ctrl+Shift+I then go to Console in Solo to see if there are any disconnect error messages that appear when you try to download.