Actually the return from an OnTouchListener should be a boolean that if True indicates that the listener has handled the event and doesn't want it propagated further to other views in the event chain. If it returns False then it tells Android to let the next listener in the event chain to be called. When I wrote the Reflection library I opted to check for this and log a warning. After the warning the Reflection OnTouchListener actually returns True to indicate that event was consumed.
To remove the warning declare Snack_Touch as returning a Boolean and return True. This is explained in the Intellisense comments for SetOnTouchListener.
it's looking for the touch indicator (up,down,etc) derived from the listener.
it seems to take into account that there may be no such indicator, in which
case it posts that message. it then consumes the even and exits.
no harm, no foul. you can check it out in the reflection.jar in the b4a internal
libs.
Actually the return from an OnTouchListener should be a boolean that if True indicates that the listener has handled the event and doesn't want it propagated further to other views in the event chain. If it returns False then it tells Android to let the next listener in the event chain to be called. When I wrote the Reflection library I opted to check for this and log a warning. After the warning the Reflection OnTouchListener actually returns True to indicate that event was consumed.
To remove the warning declare Snack_Touch as returning a Boolean and return True. This is explained in the Intellisense comments for SetOnTouchListener.