You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to implement a "Game Information" dialog somewhere in SteamTinkerLaunch that displays more thorough game information. For example, the information on the Main Menu, as well as some extra information (the Steam Deck compat information that can only be seen currently from the command line, for example). It should also be trivial to add a command-line equivalent.
I would also like some kind of STL info dialog as well, and associated command-line option alongside it. This would have links to the GitHub page, some license information, etc.
Likely both of these would have three functions each: One to fetch the information, and then one each for displaying it on a GUI and command line each.
P.S. - Instead of keeping notes on my ideas to STL to myself, I have decided to try and open/detail issues for the ones I feel are more fleshed out, for development transparency as well :-)
The text was updated successfully, but these errors were encountered:
System Information
Feature Description
I would like to implement a "Game Information" dialog somewhere in SteamTinkerLaunch that displays more thorough game information. For example, the information on the Main Menu, as well as some extra information (the Steam Deck compat information that can only be seen currently from the command line, for example). It should also be trivial to add a command-line equivalent.
I would also like some kind of STL info dialog as well, and associated command-line option alongside it. This would have links to the GitHub page, some license information, etc.
Likely both of these would have three functions each: One to fetch the information, and then one each for displaying it on a GUI and command line each.
P.S. - Instead of keeping notes on my ideas to STL to myself, I have decided to try and open/detail issues for the ones I feel are more fleshed out, for development transparency as well :-)
The text was updated successfully, but these errors were encountered: