When I say I worked for hours, I obviously do not mean coding for hours before testing every now and then, which would indeed be stupid. I meant lots and lots of change-compile-install-run cycles.
setSupportZoom(false) seemed to be the last straw, after this change my event handlers would always fire. Why messing with Zoom you may ask... Well, I noticed that accidentally double-clicking on the screen had the effect of zooming out from my content (there were BTW discussions about disabling that default on StackOverflow too). After I disabled zoom support things appeared to start working in 2.1. However, after reading your message, I commented that line out, and... things still work :-) So you may be right -- can be something else I did... The whole setup is a bit complex, and it involves GestureDetector in a subclass of WebView, etc. The annoying thing had been that handler firing in response to clicking had been inconsistent; it always worked in 2.2, and in <=2.1 it could work in the beginning and then stop working. Things DO work now, though, so I can make progress with the rest of the app :-) On Jul 16, 6:05 pm, "Maps.Huge.Info (Maps API Guru)" <cor...@gmail.com> wrote: > I tried that and it seemed to have no effect. Are you sure it was > settings.setSupportZoom(false); and not something else? If you tried > for hours, how many other changes did you make? > > -John Coryat -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
