Suggestion: VK_APPS key (i.e. popup menu key)

[Gero Zahn]

Hi Austin,

Am 27.03.18 um 07:24 schrieb Austin English:
> Hi Gero,
> 
> Where did you get that value from? I don't see it in
> https://github.com/phracker/MacOSX-SDKs/ and can't find it anywhere in
> google.

Probably because a genuine Mac keyboard does not have that key. ;-) But 
it still has a key code when connecting a PC keyboard to a Mac. I got 
the 0x6e out of Many Tricks Key Codes:
> https://manytricks.com/keycodes/

When I press and release the VK_APPS key on my Cherry keyboard connected 
to my MacBook Pro, this is what happens:

> Key Down
> 	Characters:	
> 	Unicode:		16 / 0x10
> 	Keys:		
> 	Key Code:	110 / 0x6e
> 	Modifiers:	256 / 0x100 ⓘ
> 
> Key Up
> 	Characters:	
> 	Unicode:		16 / 0x10
> 	Keys:		
> 	Key Code:	110 / 0x6e
> 	Modifiers:	256 / 0x100 ⓘ

As I mentioned earlier: I've been hand-patching winemac.drv.so manually 
for quite a while now after each new release. For wine-3.0 (through 
HomeBrew), it's as follows:

> $ xxd winemac.drv-fresh.so > winemac.drv-fresh.so.hex
> $ xxd winemac.drv-patched.so > winemac.drv-patched.so.hex
> $ diff winemac.drv-fresh.so.hex winemac.drv-patched.so.hex 
> 25998c25998
> < 000658d0: 7900 4400 0100 0000 0000 0000 0000 0000  y.D.............
> ---
> > 000658d0: 7900 4400 0100 0000 5d00 6e00 0100 0000  y.D.....].n.....
> $ 

As you can see, there's again the 0x6e / 0x100 in it, together with the 
"target key" 0x5d, as defined in
> ./include/winuser.rh
like this:
> #define VK_APPS                0x5D 

If I remember correctly, I got all those crazy winemac.drv.so patching 
ideas from this blog post:
> https://palant.de/2014/02/14/crazy-hacks-changing-wine-key-mappings-on-mac-os-x

It became necessary after I had switch from X11 wine to Mac-native wine, 
and thus patching ~/.Xmodmap didn't have any effect anymore.

Thanks for listening,

Gero