I don't know if this is supposed to be there, but I can't seem to find any documentation on a keyboard.inputs module, which leaves me using the events module and getting this warning.
I think it's the same in 0.2.5 though, I just work with 0.3+
You can see it here:
https://github.com/UPBGE/upbge/blob/master/doc/python_api/rst/bge_types/bge.types.SCA_InputEvent.rst
https://github.com/UPBGE/upbge/blob/master/doc/python_api/rst/bge.events.rst
Also you can see this old issue: https://github.com/UPBGE/upbge/issues/515
And the commit log:
https://github.com/UPBGE/upbge/commit/831d91af5ffab6773b43723fd4f536fdbdbb3270#diff-a822100daa9f255dcf4eb7a33f8bde2a
So the deprecation warning is intentional and not old bge legacy? Then I'll update the code
Teorically, we set deprecation warning to warn that we will remove after 2 release. But in this case we have kept for more.
I think we should remove it for 0.3
As you recovered .activated, .active.... which are handy, feel free to remove the old events code if you want. As you want
Ah, that's really useful
Each event has .active, .activated and .released, that actually shrinks the code 馃憤
Updated the node addon to use keyboard.inputs
Most helpful comment
As you recovered .activated, .active.... which are handy, feel free to remove the old events code if you want. As you want