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
It's possible to manually add programs but every executable is only added once. It might be beneficial to be able to add the same executable multiple times to expose different functionality through launch options.
In the upcoming Library view every game can have its own entry.
My main thought here is that most game launchers allow setting launch options which directly start a game or take you to the correct landing page.
This could also be handy to expose every single game of a launcher to other programs with bottles-cli or as a .desktop file.
Another side effect is that this will allow different feature sets of a program through launch options or scripts.
I don't have a particular example here but I can imagine this being useful to sometimes start a game in VR mode, on a special display or with a specific resolution - as long the program exposes functionality with launch options.
Same adheres for pre-run and post-run scripts.
Example of three different programs pointing to the same executable:
Also have a look at the yaml config below.
Describe the solution you'd like
It seems it's currently not working because the value in the yaml file is set to the executable name. It's already possible to do this by adding the configuration manually to the yaml file. So I guess this will need a change to an unique ID of some sort.
Changing this will also have an impact to the command line interface where it's currently possible to call a program in a bottle by the executable name which would be ambiguous then (bottles-cli run -e EXECUTABLE). Current workaround is to call bottles-cli run -p PROGRAM instead.
Example of the yaml configuration from the screenshot above:
Tell us the problem or your need
It's possible to manually add programs but every executable is only added once. It might be beneficial to be able to add the same executable multiple times to expose different functionality through launch options.
bottles-cli
or as a .desktop file.Example of three different programs pointing to the same executable:
Also have a look at the yaml config below.
Describe the solution you'd like
It seems it's currently not working because the value in the yaml file is set to the executable name. It's already possible to do this by adding the configuration manually to the yaml file. So I guess this will need a change to an unique ID of some sort.
Changing this will also have an impact to the command line interface where it's currently possible to call a program in a bottle by the executable name which would be ambiguous then (
bottles-cli run -e EXECUTABLE
). Current workaround is to callbottles-cli run -p PROGRAM
instead.Example of the yaml configuration from the screenshot above:
Other solutions?
Additional context and references
No response
The text was updated successfully, but these errors were encountered: