andymanic
commented
1 year ago I did try a tabbed layout during development but a mix of the tools WinForms has available and other UI choices made it better to have a single page. The results viewer is purposefully a separate window as you can open multiple copies to compare results. The UI definitely isn't perfect, but I don't think I'll be going down this route right now. I'll leave this issue up and if more people want to upvote it then I can consider it.
Im thinking a tabbed method of UI that can be compact with the last used function/settings as the saved profile so Presets are not needed.
Tabs=Test Source DirectX Tool renamed to Display. (this function is solely to test displays) Mouse/Keyboard renamed to Input devices. (controllers and other devices can be tested) Game renamed to Games and Apps? (Is there any difference or need for External?) Audio
Each tab opens the avaliable settings to the testing method, this is make settings easier to choose rather than have stuff automatically switch for you.
DirectX Tool - Display: Test display. Trigger Type - OSLTT Button and 2 pin Input. Auto clicker. Sensor Type - Light.
Mouse/Keyboard - Input Devices: Trigger Type - Audio. Sensor Type - Light Sensor and Clicks/Keypresses.
Game - Game and Apps: Trigger Type - OSLTT Button and 2 pin Input. Sensor - Light
Audio: Trigger OSLTT Button. Sensor Type - Audio.
Each tab with no options to change certain setting will state what type is used rather than none shown. For example Sensor type - Audio sensor, will show the sensor is audio based.
The help, debug and results viewer can be on the same tab like layout.
The results viewer can become a tab to select rather than a detached window, with a list of historical tests and time of the tests. Sorta like CapframeX
https://i.imgur.com/TphpDYb.jpeg