How to capture the end of a Zoom In/Out animation from a MapController

by rajesh.singh » Sat, 29 Jan 2011 03:07:32 GMT


Sponsored Links
 Hello,

Just an interesting query here, is there a way to capture when a zoom
animation sequence has ended when calling either:

MapController.zoomIn() or MapController.zoomOut();

I know that it does kick off an animation sequence to zoom in/out to
the next level, however there is no known way I can find/google
search, etc to find out when it finishes that sequence. I need to be
able to run an update command when that is stopped so my map updates
correctly.

I've found that by running the update command after calling the above
function the Projection isn't from the zoom out level but somewhere
inbetween (so I can't show all the data I need).

Any ideas?

Cheers,
Raj

-- 



Re: How to capture the end of a Zoom In/Out animation from a MapController

by TreKing » Sat, 29 Jan 2011 03:59:48 GMT


 



Not really, the Maps API is really lacking in this regard (well, in a lot of
regards, actually, but we'll focus on this one).

What's been suggested before is for you to track the zoom level yourself,
perhaps on each Draw() call, since you know this is triggered when the map
has been invalidated (which happens on a zoom). Check the zoom level there
and if it's different, trigger your update (or kick off your own
ZoomChangedListener).

-------------------------------------------------------------------------------------------------
TreKing < http://sites.google.com/site/rezmobileapps/treking> ; - Chicago
transit tracking app for Android-powered devices

-- 


Sponsored Links


Other Threads

1. How to get the SDK running on fedora

I decided to try to run the SDK on a x86-64 fedora install. It is not
to hard to get working once you know the packages you need. The things
I had to install to get the emulator working

glibc-2.9-3.i386
libX11-1.1.4-6.fc10.i386
gdbm-1.8.0-29.fc10.i386
libao-0.8.8-5.fc10.i386
libXau-1.0.4-1.fc10.i386
alsa-lib-1.0.18-6.rc3.fc10.i386
alsa-plugins-pulseaudio-1.0.18-1.rc3.fc10.i386
libXcursor-1.1.9-3.fc10.i386
libgcc-4.3.2-7.i386
libXdmcp-1.0.2-6.fc10.i386
libXext-1.0.4-1.fc9.i386
libICE-1.0.4-4.fc10.i386
e2fsprogs-libs-1.41.3-2.fc10.i386
libselinux-2.0.73-1.fc10.i386
audiofile-0.2.6-9.fc10.i386
libstdc++-4.3.2-7.i386
libxcb-1.1.91-5.fc10.i386
libXrender-0.9.4-3.fc9.i386
libasyncns-0.7-1.fc10.i386
libSM-1.1.0-2.fc10.i386
glib2-2.18.3-2.fc10.i386
esound-libs-0.2.41-1.fc10.i386
gpg-pubkey-4ebfc273-48b5dbf3
zlib-1.2.3-18.fc9.i386
libXrandr-1.2.3-1.fc10.i386
pulseaudio-libs-0.9.13-6.fc10.i386
libXfixes-4.0.3-4.fc10.i386
ncurses-libs-5.6-20.20080927.fc10.i386
libcap-2.10-2.fc10.i386
gamin-0.1.9-6.fc10.i386

This might be more than the minimum. I just used strace and installed
everything it tried to open :-)

To get the eclipse integration working you will need:

tomcat5-jasper-eclipse-5.5.27-6.1.fc10.noarch
eclipse-swt-3.4.1-5.fc10.x86_64
icu4j-eclipse-3.8.1-4.fc10.x86_64
eclipse-jdt-3.4.1-5.fc10.x86_64
eclipse-demos-0.0.1-2.fc8.noarch
eclipse-gef-3.4.1-1.fc10.x86_64
eclipse-ecj-3.4.1-5.fc10.x86_64
eclipse-platform-3.4.1-5.fc10.x86_64
eclipse-rcp-3.4.1-5.fc10.x86_64

After installing this packages the android integration should just work.

Cheers,
Rafael

--~--~---------~--~----~------------~-------~--~----~

2. Bug, voicemail setting reset at boot

Hi all.  I prefer to use a different voicemail system than the one
provided by my carrier, one I have been using for a few years.  (If
you care: It uses GSM redirects to make some class of incoming calls
forwarded to a particilar number.  I use Youmail.)

Anyway, the upshot is that the number I want dialed at long-click '1'
in the dialer is not the same as what the phone came with.

I set the new number in the phone settings, and all is well until next
boot.  Then it's reset to the default number my carrier suggests/
provides.  To recreate:

 - go to settings, call settings, voicemail. Note your voicmail
number.
 - Change it to '+17142043114'.  Save.
 - Reboot.
 - Go back to voicemail setting.  Note it is back to the original.

---

Firmware v1.0
Baseband v62.33.20.08H_1.22.12.29

--~--~---------~--~----~------------~-------~--~----~

3. natvie code try/catch statement support or not

4. Adding a GridView to a TableRow.

5. Usage of ArrayAdapter leads me to Index Array out of Bounds Exception

6. When will star the Android Developer Challenge II ?

7. onProviderEnabled / onProviderDisabled unexpected behavior