Currently, the .desktop files that are generated via Q4Wine do not include a custom StartupWMClass property. This allows for a better distinction of separate applications, allowing desktops to group them in a more relevant way (a link explaining this is over here).
As such, it would be nice if Q4Wine automatically generated this for its .desktop files - a workaround exists in manually renaming them, but these changes won't last after a modification through Q4Wine. The value of StartupWMClass should be the same as the name of the currently targeted executable, explained in the above link: StartupWMClass=<name of the exe-file>
Currently, the .desktop files that are generated via Q4Wine do not include a custom StartupWMClass property. This allows for a better distinction of separate applications, allowing desktops to group them in a more relevant way (a link explaining this is over here).
As such, it would be nice if Q4Wine automatically generated this for its .desktop files - a workaround exists in manually renaming them, but these changes won't last after a modification through Q4Wine. The value of StartupWMClass should be the same as the name of the currently targeted executable, explained in the above link:
StartupWMClass=<name of the exe-file>