Closed GoogleCodeExporter closed 8 years ago
I guess you are working with the latest SVN version because this behaviour is a
result of the possibility to let input events bubble up the component hierarchy
which was recently added.
So what happens is that when no input processor is registered with a component
the default behaviour is to bubble the events up to its parent which is why you
drag "a" when dragging "b".
The default behaviour of each input processor is to stop the input event
propagation unless stated otherwise (e.g.
tapProcesssor.setStopPropagation(boolean)).
So to get the behaviour that you expected in your Issue you could do this:
b.addInputListener(new IMTInputEventListener() {
public boolean processInputEvent(MTInputEvent inEvt) {
inEvt.stopPropagation();
return false;
}
});
This input bubbling was recently added and im still open for
comments/suggestions. But this should explain the behaviour you are getting.
Original comment by sirhc.f...@gmail.com
on 16 Nov 2010 at 5:03
Original comment by sirhc.f...@gmail.com
on 11 Feb 2011 at 10:25
Original issue reported on code.google.com by
mattsl...@gmail.com
on 19 Oct 2010 at 1:06