From idan...@gmail.com on September 24, 2011 16:03:32
Currently, the logic in MapView is integrated with MapActivity. That didn't use to be a problem until Fragment was introduced in Honeycomb.
This makes it impossible to use a maps fragment as part as an activity. You can in theory use a MapActivity, but this solution is not clean and may affect other fragments.
I've managed to workaround the issue by refactoring MapActivity and MapView, so that MapActivity actually implements a new interface named MapContext which MapView relies on instead.
Attached is the patch I'm currently using. I have also created MapFragment which is not part of the patch, and is being used here: https://market.android.com/details?id=org.idansof.otp.ui&feature=search_result https://code.google.com/p/otp-android/
Attachment: mapsforge-mapcontext.patch
Original issue: http://code.google.com/p/mapsforge/issues/detail?id=177
From idan...@gmail.com on September 24, 2011 16:03:32
Currently, the logic in MapView is integrated with MapActivity. That didn't use to be a problem until Fragment was introduced in Honeycomb.
This makes it impossible to use a maps fragment as part as an activity. You can in theory use a MapActivity, but this solution is not clean and may affect other fragments.
I've managed to workaround the issue by refactoring MapActivity and MapView, so that MapActivity actually implements a new interface named MapContext which MapView relies on instead.
Attached is the patch I'm currently using. I have also created MapFragment which is not part of the patch, and is being used here: https://market.android.com/details?id=org.idansof.otp.ui&feature=search_result https://code.google.com/p/otp-android/
Attachment: mapsforge-mapcontext.patch
Original issue: http://code.google.com/p/mapsforge/issues/detail?id=177