Add global compatibility configuration feature#3
Add global compatibility configuration feature#3Ingan121 wants to merge 2 commits intonbusseneau:masterfrom
Conversation
|
Thanks for the PR! I actually didn't know about
Yep... Technically it's still the case, as setting I'm actually curious as to whether the environment variable overrides compatibility tab, or the other way around, I will have to play with it. |
|
any updates on this? |
|
Sorry, I did not take the time required to properly test this PR nor integrate it. Is that feature something you'd need? |
|
it would be quite useful for a lot of people as i think that people just want to disable fullscreen optimisations globally instead of per application |
|
i agree, a global option would be great |
It is possible to set a global compatibility option by using an environment variable named __COMPAT_LAYER, so I added a feature to change it easily.
(The auto-generated comments of Strings.Designer.cs were changed to Korean because my system and VS language is Korean, and it seems there is no simple way to change them to English without completely replacing my VS language by installing the English language pack. I think doing a simple task with English VS will change that back to English.)
(Btw, I did this after seeing many articles saying 'there is no way to disable the fullscreen optimization globally after 1809'.)