PathOverlay does not handle transparency well; drawn path more opaque at joints

[GoogleCodeExporter]

What steps will reproduce the problem?
1. inherit from PathOverlay
2. call setAlpha() with any non-opaque value
3. call mPaint.setStrokeWidth() with a sufficiently thick value
4. call addPoint() to create a path consisting of two or more sections
5. display the result on the map.

What is the expected output? What do you see instead?

The expected output is a path with uniform alpha value. Instead, we get more 
opaque joints, as the separately drawn path segments overlap there.

What version of the product are you using? On what operating system?

OsmDroid 1.09 .. 3.01, Android 1.5 .. 2.3 (all intermediate versions are 
affected, too)

Please provide any additional information below.

Original issue reported on code.google.com by nagydani...@gtempaccount.com on 11 Feb 2011 at 12:43

[GoogleCodeExporter]

This can be fixed by using a Path rather than drawing a series of lines. This 
would also allow us to do path-click detection more accurately rather than 
doing a smallest-enclosing-rectangle hit test.

Original comment by kurtzm...@gmail.com on 25 Feb 2011 at 6:52

• Changed state: Accepted

[GoogleCodeExporter]

Actually, android does not have Path hit-testing. boo! We should still use a 
Path however.

Original comment by kurtzm...@gmail.com on 26 Feb 2011 at 11:30

[GoogleCodeExporter]

This issue was closed by revision r835.

Original comment by kurtzm...@gmail.com on 27 Feb 2011 at 4:56

• Changed state: Fixed