Hakan...
I confirm the duplicated chart groups on second settings invocation.
Funny, I had fixed this, and also the previous problem with Mariners Standard list corruption, on my local build. But I guess an inadvertent "git reset" blew them away before they got committed. And then I went off chasing some other shiny object, and forgot...
I'll fix them again.
Not sure why your W10 should be so slow to start. I know that Windows Debug builds are slow to start, because building the Options dialog does a lot of memory allocation, and Windows Debug builds by default do extensive memory bounds and consistency checking. This is slow. This checking is not done in Release builds.
Preloading the Options dialog is a judgement call. I can see that it might be a little irritating to experienced testers on a slow machine. Testers and developers are very used to starting O and immediately entering Options dialog to test one thing or another. Who wants to wait?
On the other hand. I think it is important that when a user,
especially inexperienced user, clicks a button, then something should happen visually RIGHT NOW. Otherwise, the user feels like they are not in control of their PC, and uncomfortable. The "something visual" could be a spinner or progress dialog, which is better than nothing. But far better to have the correct action just pop up in less than 1 second.
But it is a judgement call. Opinions?
Thanks
Dave