However, it's confusing how the UI is laid out here. The window opens with the first item in the list of sceneries 'selected' (Mount Dauphin) without me clicking on anything. And because the color of the selected line item is very similar to the main window, it wasn't clear to me that it was 'selected'. This led to me clicking the 'Update 1 Selected' button but getting confused when the all I saw was a brief view of the progress bars and then nothing. Once I figured out that the first line item is always selected, and the brief appearance/disappearance of the progress bars is because I (obviously) don't have that scenery installed, it makes sense - but it's confusing at first, and I can pretty much guarantee you it'll be confusing to other users as well.
There's an old saying in UI design that, regardless how much effort you put into something that looks perfectly logical to you, somebody WILL find confusing it anyway. So, you think it's JUST a matter of making the selection color lighter ?
In any case, there was a reason why the first product in the list was selected by default, and it's because in P3D it's GSX, which is *by far* our most popular product so, lots of users only know GSX and identify FSDT with GSX, and assume the updater is a "GSX updater" so, THEY didn't know what to do, so we pre-select the first product on the list (GSX), so they could just click Update.
But generally, at least until GSX for MSFS is out (it will surely be at the top of the list), it's best not select anything at start.
Probably it would be best to not selected a scenery in the list by default, and change it so it's clearer which one is selected once the user clicks/selects it.
Ok, it's done in the current version that is online now. At start nothing is selected, and the selection color is lighter now. Also, you can go back to "no selection" by clicking outside the list.
Also, the 'Update 1 Selected' button should either be grayed out or just not appear at all if a scenery is selected that the user doesn't own/is not installed yet.
That's changed as well in the current version. The "Update Selected" button won't be active if you have selected something you don't have. If you select multiple products at once, it will be active only if *all* of them are installed.
Oh, just realized that the Universal Installer did not update itself to the new version you posted - I had to go to the FSDT website and download it from there. Is that the intended method?
Obviously not. The whole point of having a two step process ( which had the side effect you didn't like as the extra window in the background ), is precisely so the update can "Update itself". The extra window you see is the 1st stage update, which doesn't do *anything*, other than checking if there's a new version of the 2nd stage updater to download, which does the actual work, so it will be automatically started by the 1st stage.
Also, with the updater split in two, there would be any need to notify an update, ask you if you want to download the new version, and then quit and restart, each time there's an update.
So no, it's not normal you had to download the installer again.
Also, it's still not giving me start menu shortcuts, just the two on the desktop on install.
Something's wrong with your downloads, because the current version of the installer we have online now, surely does create the two extra icons in the Start button menu. Note that, because you are not downloading from our server, but from a cache replicated on Cloudflare network of 260+ nodes, it's possible your local Cloudflare node still hasn't replicated the updates we just released. Usually, it doesn't take much, like 10-15 minutes or few hours, but in some cases it might be up to 24 hours before all nodes gets all the updates.
This would explain why the updater didn't update itself and why the installer didn't create the extra icons: you are still using the old version.
So, try again now, the changes to the UI should be easy to recognize and, in any case, the updater .EXE version ( and the installer version ) is 2.0.2.26. Let me know if you are getting it, and if it fixed the crashes you had with the update from the list.
It might be possible to get rid of the 1st window by Terminating it from the 2nd program, but it's not something I'm sure it will always work, there might be unexpected side effects, because the child process is killing is caller so, I need to be sure this is something safe to do, under all possible permission and account settings.
