Thank you for your prompt reply.
Well it seems I have got straight to the
'culprit', and possible 'fixer' ;=))
1. Ctrl + Key input difference
Look forward to the 'fix' for the non-cross
platform CTRL + SPACE yielding just 'space'
As you would understand this return of a
'space', instead of 0, in WIN32, also messes
up any active PUI widget (through puKeyboard()),
by adding a space to the input!
And seemingly incorrectly returns 0 from
puKeyboard(), even though it used the key?
But maybe mis-understand widget inputs ;=((
2. Special Key Callbacks
As to the modifier key callbacks,
I note from an SVN browse that is was you
that introduced the CTRL, ALT, and SHIFT
(CAS) key down, call backs, with revision 868
by fayjf, Mon Jan 4 04:44:34 2010 UTC.
AND, I can now see you did attempt to ALSO
add a Key UP callback, if the app has
registered a 'SpecialUp' call back! Which
I did not even know about!
Maybe this was to satisfy a 'request' to
be able to SEPARATE left CAS from right
CAS keys, but unsure why this would be
Although I know on European keyboards, and
others, the right-alt key is an extra special
so called _Alt Gr_ modifier to address a 3rd
key type on those keyboards, not present on
But as stated, in any event, an INVOKE_WCB
'input callback' then should NOT output
a warning if the app calls glutGetModifiers()
in those circumstance.
Or else you face a massive documentation
nightmare to explain WHY, in these special
circumstance, calling glutGetModifiers()
is NOT allowed/expected ;=((
PS: On subscribing, I inadvertently selected
digest mode, but have now 'corrected'
Get latest updates about Open Source Projects, Conferences and News.