crankDocked(), crankUndocked() in Input Handlers

SDK Feature Requests
1

I'm going to try it anyway in case it works undocumented... but the docs don't list docking/undocking as able to be assigned in an InputHandler table:

Those can be two important inputs—I use them to initialize/process info relating to crank input.

3 Likes
2

That's a good point. That would be useful.

I implemented something like that in my own framework and this is really useful. That should be part of the SDK.

2 Likes
3

Maybe this is a documentation omission... unless I'm being dense, it seems to "just work" despite the docs suggesting otherwise!

(I thought it would take longer to port all my inputs over to InputHandlers... went very smoothly.)

4

Yes, documentation omission, sorry. We'll get that fixed.

2 Likes
6

Cool. I wonder if any other inputs are omitted in the docs there but functional? Like Accelerometer? gameWillResume()?

2 Likes
7

Looking at the source code, the full list is:

const char* functionNames[] = {"AButtonDown", "AButtonHeld", "AButtonUp", "BButtonDown",
  "BButtonHeld", "BButtonUp", "downButtonDown", "downButtonUp", "leftButtonDown",
  "leftButtonUp", "rightButtonDown", "rightButtonUp", "upButtonDown", "upButtonUp",
  "cranked", "crankDocked", "crankUndocked"};

So just those two extra, no others.

3 Likes
8

Thanks. Just wondering!

12

Sorry to raise a dead thread, but I was hoping to give this some attention again since (as of 2.6.2) the documentation still omits these handlers. At least in the part prefaced by

The following functions can be defined in your custom inputHandlers table:

1 Like
13

Turns out this was never filed in our issue tracker. I have filed it now. Thanks for bringing it back to our attention.

2 Likes