Function keys only working after hotkey remap

[elabx]

I am new to Wings3D and through my process of learning the interface I noticed that F6 and F7 (which default to next loop/previous loop) only work if I remap them, other hotkeys seem to work fine aside from the ones asigned to the function keys.

My keyboard is a Mac USB Keyboard with numerical keypad in english.

Wings version : 1.5.3
OS: OS X 10.9.4

I tried this in version 1.5.2 and 1.5.3

Wings3D is such a great piece of software

[tkbd]

(07-16-2014 04:47 PM)elabx Wrote:  I am new to Wings3D and through my process of learning the interface I noticed that F6 and F7 (which default to next loop/previous loop) only work if I remap them, other hotkeys seem to work fine aside from the ones asigned to the function keys.

My keyboard is a Mac USB Keyboard with numerical keypad in english.

Wings version : 1.5.3
OS: OS X 10.9.4

I tried this in version 1.5.2 and 1.5.3

Wings3D is such a great piece of software

Hi elabx
Thank you to share this problem.
I also have the same situation...

To Programmers.
In OSX, in some special key...
The key code value has been assigned a different value as Windows.

This is when you register to "Page UP" key hot key in Wings3d of OSX will be displayed <63276> on RMB Menu.
From this fact, it is code value indicates that you have over 60,000.

Followed a source code Wings3D seems to use the constants of ESDL the key code.
SDLK_F1 in wpc_hotkey.erl
Probably ESDL-related bugs.

Here is corresponding function key's code on OSX.

Quote:'63236':F1
'63237':F2
'63238':F3

This was also seen in the library other than SDL.
https://www.allegro.cc/forums/thread/606860

and more about OSX's Keycode List is here.
It seems that AppleWebKit use these also.

Code:

'63232':UP
'63233':DOWN
'63234':LEFT
'63235':RIGHT
'63236':F1
'63237':F2
'63238':F3
'63239':F4
'63240':F5
'63241':F6
'63242':F7
'63243':F8
'63244':F9
'63245':F10
'63246':F11
'63247':F12
'63273':HOME
'63275':END
'63276':PAGE_UP
'63277':PAGE_DOWN
'63302':INSERT

-------
tkbd

[starsima]

hi i have the same bug its good to found this topic