Is there anyway to handle the “back” key only for single containers (or conditions)?

Is there anyway to handle the “back” key only for single containers (or conditions)?

Handling it globally by script pretty much destroys it’s functionality to i.e. scroll back a panel.

In my case, when pressed in an opened and scrolled panel I do NOT want “back” to scroll back, but I need to execute more/other actions by script.

]]>

3 Commentsto Is there anyway to handle the “back” key only for single containers (or conditions)?

  1. Anonymous says:

    < ![CDATA[

    Can’t you just override the back action and check if it was launched from the desired panel or not?



    Of course the best will be to allow custom back action in containers ( Pierre Hébert, that’s yours) but from script it could be done checking if the container need a custom script, otherwise just perform the default action (from script, not obvious but I think I know how to do it)

    ]]>

  2. Anonymous says:

    < ![CDATA[

    TrianguloY Will try again, but last time checked there was no origin retrievable.

    ]]>

  3. Anonymous says:

    < ![CDATA[

    Sorry for the delay. Keys handling differs from touch events because keys are not targeted to a specific UI component, hence they are managed globally and not sent to a particular component (view). There is some kind of focus management for containers, but there is no visual indication of this and it can change often and in subtle ways. For this reason I think this is rather unsafe to link a key event to a container (or any other item).

    ]]>

Leave a Reply

Your email address will not be published. Required fields are marked *