mirror of
https://gitlab.winehq.org/wine/wine-staging.git
synced 2024-11-21 16:46:54 -08:00
3d74da6622
Instead we have an alternate code path for the appropriate API entry points in uxtheme.dll. This is not the best organizational structure. We should probably have HTHEME handles resolve to an object with its own function table, so then we have an MSSTYLES backend and a GTK backend and what have you. It would also be better to avoid having GTK controlled with its own registry key like this but rather to have it be selectable using EnumThemes()/ApplyTheme() [presumably through a fake theme file, as was used in the original implementation], so that we don't have to have special handling for those functions and everything can just be part of the HTHEME backend. However, time is currently of the essence, and this will have to do for the moment. |
||
---|---|---|
.. | ||
0001-winecfg-Add-staging-tab-for-CSMT.patch | ||
0002-winecfg-Add-checkbox-to-enable-disable-vaapi-GPU-dec.patch | ||
0003-winecfg-Add-checkbox-to-enable-disable-EAX-support.patch | ||
0004-winecfg-Add-checkbox-to-enable-disable-HideWineExpor.patch | ||
0005-winecfg-Add-option-to-enable-disable-GTK3-theming.patch |