Closed vorot93 closed 11 years ago
Started work on prepend in 'prepend' branch. Might need a hand for implementing prepending.
Personally I see no sense in this option.
q4wie has support for wine template string: http://q4wine.brezblock.org.ua/documentation/en_us/10-prefix-settings.html#advanced
this totally cover "Prepend cmd" use case. And most of other use cases such "Run in separate X session", "pre run" etc.
It much more flexible then adding separate option which will just add complexity to the ui and source code .
So it is better to construct wine template string for optirun users and publish it on q4wine documentation site.
I disagree. IIRC the execution template is prefix-wide while we need something icon-specific. Also there is a huge difference between prepending one's cmd and writing the whole execution string anew. The latter might ruin q4wine installations in case default string changes in the future.
By forcing end users to write own scripts we just ruin the whole idea of q4wine: make wine experience as seamless as possible.
Q4Wine needs to have support for commands that are prepended to wine. For example: optirun wine program.exe
This is required for optimus notebook owners who need to prepend optirun to use NVIDIA GPU.