connecting with bad certificate in background profile shows certificate window from current profile

[atari2600tim]

Brief summary of issue / Description of requested feature:

I have a shortcut for release version of Mudlet that opens my main set of profiles. It's similar to the open profile on start checkbox except I don't have secondary instances open those profiles. You can test this out either way if you want. Anyway, if you open two profiles with an error on the first one, then when it opens the window to tell you about the error, it will be on the second profile.

Steps to reproduce the issue / Reasons for adding feature:

1. create a profile named "badcert" set to badcert.timmud.com 5556 with the secure checkbox enabled
2. open command prompt
3. change directory to the public test build, something like cd C:\Users\Alpha\AppData\Local\Mudlet-PublicTestBuild\app-4.17.2-ptb02293acc
4. Start the program with "Mudlet PTB" --profile="badcert" --profile="BatMUD"
5. It will bring up profiles badcert and BatMUD. Both profiles are instantly opened and focus is left on final one, and then each take a moment of network traffic to connect. There is an error message on one and welcome screen on the other. The settings window comes up to show you the certificate message, but it is showing BatMUD instead of badcert profile.

Error output / Expected result of feature

Open that window but for the impacted profile. Possibly switch focus to that profile as well?

Extra information, such as the Mudlet version, operating system and ideas for how to solve / implement:

I've only tried this on Windows 10 so far