Reorder call to overlay and super dispatchTouch()

[GoogleCodeExporter]

When we draw, we do it overlays-first and then the call to super after that. So 
the overlays get drawn "beneath" the draw call to super which should draw any 
the child-views that the maps contain on top of the overlays.

When we dispatch touch events, we dispatch them to the overlays-first, and then 
to the super. So the overlays get the touch event first (and can consume them 
first) before the views.

The touch events are backwards. Just like how we reverse the overlays, so that 
the last drawn (or what gets drawn above all other views) gets the touch event 
first, we should allow the super call (which gets drawn last) to get touch 
events before the overlays.

This is a little bit of a breaking change - but only in the sense that is was 
wrong before - so I will submit this issue for public comment before we make 
the change.

Original issue reported on code.google.com by kurtzm...@gmail.com on 7 Jun 2013 at 9:05

[GoogleCodeExporter]

This issue was updated by revision r1243.

Reverse the order of touch event dispatch for overlay and super. This allows 
views that will draw on top of the overlays to receive touch events first.

Original comment by kurtzm...@gmail.com on 14 Jun 2013 at 7:16

[GoogleCodeExporter]

Original comment by kurtzm...@gmail.com on 14 Jun 2013 at 7:32

• Changed state: ReadyForTesting

[GoogleCodeExporter]

Issue 219 has been merged into this issue.

Original comment by kurtzm...@gmail.com on 24 Jun 2013 at 12:47

[GoogleCodeExporter]

This has been released in 4.0.

Original comment by kurtzm...@gmail.com on 25 Oct 2013 at 1:48

• Changed state: Fixed