documentation for InputDelegate, BehaviorDelegate events handling flow

Is there a documentation for input events? What I'd like to understand for each method in InputDelegate, BehaviorDelegate is what happens if it returns true / false. I mean what will be the flow of the method calls.

i.e (theoretically, just to explain myself):

onDrag -> onSwipe -> onFlick -> onNextPage(if direction is up) / onPreviousPage(if direction is down) - the next function is only called if the previous returned false (I see in the simulator that this is not the case, this is just an example)

  • Have you looked at the input sample in the SDK?

    Basically, return true if your app is handling the event, false if you want the system to handle it.  In most cases, you want to return true.  The va and venu are a bit picky about this.

    About the only time I return false is if I want an app to terminate from onBack..

  • Previously I read the documentation and now looked at the Input sample. The problem is that it doesn't answer my question, because what I try to do is a custom picker. I have it more or less working on devices with 5 buttons, using the behaviours. This means I can choose a letter by pressing the up/down buttons. The letters change on every click.

    My next step would be to make it work more reasonably on touch devices and make the letter choice faster by implementing some other "thing". I am trying to use the onFlick and onDrag. I can log the events, but I see that not all of them are implemented in all devices, however where they are implemented there all of them are called, no matter whether I return true or false in any or all of them. I thought that there is some kind of "priority" between the different events, so that I can use one of them, and by returning true preventing the system to call some of the other functions. Now I "mapped" up/down swipes to the prev/next page and it works (except that it's strange on edge devices) But now I'm trying to add flick or drag, and since both onDrag, onSwipe, onFlick are called if I'll map them also to prev/next page then I'll get too many pages changed...

  • Look at using onNextPage(). onPreviousPage() and onTap()

    Be careful with onFlcik, onDrag, as a number of touch devices don't support those

    And on some devices, a swipe to the right will be seen as onBack.