| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Happy new year to the wonderful Godot community!
|
| |
|
|
|
| |
Seems like this property isn't present on some gamepads...
Fixes #10958
|
| | |
|
| | |
|
| |
|
|
|
| |
The ID property for InputEvents is set by `SceneTree` when sending the event down the tree.
So there's no need for the platform specific code to set this value when it will later be overriden anyway...
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I can show you the code
Pretty, with proper whitespace
Tell me, coder, now when did
You last write readable code?
I can open your eyes
Make you see your bad indent
Force you to respect the style
The core devs agreed upon
A whole new world
A new fantastic code format
A de facto standard
With some sugar
Enforced with clang-format
A whole new world
A dazzling style we all dreamed of
And when we read it through
It's crystal clear
That now we're in a whole new world of code
|
| |
|
|
|
|
|
| |
Now InputDefault is responsible for giving out joypad device IDs to the platform, instead of each platform handling this itself.
This makes it possible for c++ modules to add their own "custom" gamepad devices, without the risk of messing up events in case the user also has regular gamepads attached (using the OS code).
For now, it's implemented for the main desktop platforms.
Possible targets for future work: android, uwp, javascript
|
| |
|
|
| |
Named this class in GodotCase, so it fits with the rest of the codebase.
|
|
|
Some parts were forgotten in 547a577.
|
