5 Commits

Author	SHA1	Message	Date
James Ross-Gowan	0563eb914f	win32: add Windows 10 compatibility GUID ... This suppresses the Program Compatibility Assistant on Windows 10. mpv is regularly tested on Windows 10, so this should be okay.	2015-12-20 21:06:02 +11:00
wm4	5595251447	win32: fix/change application name ... Pointed out in #935 (again).	2015-02-09 20:44:09 +01:00
wm4	ee57f7fdae	win32: edit resource files, in particular set CompanyName ... Setting CompanyName (probably) helps with issue #256. Update some other fields as well, because why not. (They're full of MPlayer remnants.)	2013-09-23 01:44:09 +02:00
James Ross-Gowan	3e7d483ac8	w32: update manifest for high DPI and Windows 8.1 ... Since Windows Vista, when running at 144 DPI or higher with composition switched on, applications that don't declare themselves to be DPI aware are stretched by the window manager, kind of like low resolution apps in OSX. To avoid this, declare DPI awareness in the manifest. Since mpv is practically resolution independent this shouldn't cause any trouble. The 'True/PM' value declares per-monitor DPI awareness in Windows 8.1, so that the mpv isn't shrunk when moved from a high DPI screen to one with a lower DPI. Also, avoid compatibility shims by declaring compatibility with all Windows versions from Vista to 8.1 and add the missing uiAccess attribute to the requestedExecutionLevel element.	2013-07-14 16:10:23 +02:00
wm4	dfcfe05885	build: fix compilation on Windows (manifest files)	2012-10-20 20:03:13 +02:00