Well i took the MarkersOverlay demo project, updated it's Click and LongClick event handling subs so they both returned True and gave it a test.
Does the attached project work as expected for you?
Martin.
Thanks. It just keeps getting stranger and stranger…
I misspoke before. If I do a MarkerOverlay_LongClick I also get a TouchEventsOverlay_LongClick, not a MarkerOverlay_Click as I had previously stated.
The project you attached works correctly in my testing with the latest "GetBoundingBox" (3.54) library.
I also modified your project a little bit to make it look more like my code. I added a touch overlay and moved the AddOverlay methods to add the scale bar,
touch overlay, followed by the marker overlay – in that order. In the marker overlay long click I added a message box. I removed the MiniMap.
With my modifications, it also works.
I took a project from about a year ago using an older library (3.4, I think). The APK built about a year ago works as expected – no touch overlay longclick when I do a marker overlay longclick.
I compiled this project using the newer, 3.54, library. Now it doesn't work – I get a touch overlay long click when I do a marker overlay longclick, but I did not modify the code at all so the callback events don't return a Boolean.
I can't imagine what's going on in my code. It's basically the same as the attached project as far as OSMDroid is concerned, but of course with a bunch of other stuff added.
Any ideas what it may be. I'm thinking I may not be returning a Boolean, but every return path looks correct. I have a button with the activity as a parent that's in front of the map and overlays. Could that be causing the problem? I will try removing that.
One solution would be for me to use a flag to disable touch overlay long clicks within 500 ms or so of a marker overlay long click – but I'd rather find the real problem.
Barry.