On new startup without QTS configuration directory, Starting QTS will result in directory being made and QTS shutting down without any user feedback. User is left to wait to see if program will open, which it will not.
Re-opening QTS will present prompt to configure server connection, server screen will open. control flow needs to be directed appropriately with consideration to UX.
Cancelling screen will load into QTS, this does not make sense.
Entering a working server config and pressing OK will prompt to restart
Pressing OK without a valid server config initiate prompt to restart, restart will take an exceptionally long time and will not trigger reconfig. Application creates empty server configuration?? Does QTS blindly execute this?
Window active/focus/layering does not work correctly 100% of the time
See video qts222_new_server_setup_experience for examples
On new startup without QTS configuration directory, Starting QTS will result in directory being made and QTS shutting down without any user feedback. User is left to wait to see if program will open, which it will not.
Re-opening QTS will present prompt to configure server connection, server screen will open. control flow needs to be directed appropriately with consideration to UX.
Window active/focus/layering does not work correctly 100% of the time
See video qts222_new_server_setup_experience for examples