5 Commits

Author	SHA1	Message	Date
James Ross-Gowan	037c7a9279	w32_common: handle media keys ... This was attempted before in fc9695e63b, but it was reverted in 1b7ce759b1 because it caused conflicts with other software watching the same keys (See #2041.) It seems like some PCs ship with OEM software that watches the volume keys without consuming key events and this causes them to be handled twice, once by mpv and once by the other software. In order to prevent conflicts like this, use the WM_APPCOMMAND message to handle media keys. Returning TRUE from the WM_APPCOMMAND handler should indicate to the operating system that we consumed the key event and it should not be propogated to the shell. Also, we now only listen for keys that are directly related to multimedia playback (eg. the APPCOMMAND_MEDIA_* keys.) Keys like APPCOMMAND_VOLUME_* are ignored, so they can be handled by the shell, or by other mixer software.	2017-08-05 02:38:44 +10:00
wm4	c9696a1b14	w32_common, w32_keyboard: change license to LGPL ... All authors agreed.	2017-06-24 12:54:45 +02:00
wm4	1b7ce759b1	Revert "win32: add mappings for some special keys" ... This reverts commit fc9695e63b. Users were complaining that both mpv and something else (what? I don't know) respond to some multimedia keys, such as volume change.	2015-06-24 15:14:38 +02:00
wm4	fc9695e63b	win32: add mappings for some special keys ... Untested.	2015-05-12 23:01:32 +02:00
James Ross-Gowan	32c0df1b53	w32: use the w32_common keymap in terminal-win too	2014-01-19 14:42:15 +01:00