Hi Carl, > I would say it is a bug as > 1) there is no way to query the implementation if only integer > zoomlevels are supported. Nokia plugin does not work at all if you eg. > zoom in from 5, 5.1, 5.2,....6.0, 6.1 (at 6.1 the map goes totally > blank.)
The blank map is definitely a bug - which I've just added and can be tracked via http://bugreports.qt.nokia.com/browse/QTMOBILITY-732 Querying for whether fractional zoom levels are supported is a also bug, but at least it's a bug of omission rather than a bug through broken stuff :) http://bugreports.qt.nokia.com/browse/QTMOBILITY-733 Thanks for the report and for the suggestion. > 2) it is possible to implement linear zooming also with bitmap tile > implementations, just by scaling the bitmaps by qreal > > It is good to have it qreal; both bitmaptile based and vector based > need it. I agree. If we were less pushed for time we might have had this in the release. We were scrambling a little to understand the various aspects of performance on devices and how fractional zooming was going to affect that performance, and so it got pushed back based on that. Once we've put out the more brightly burning fires we'll revisit it. http://bugreports.qt.nokia.com/browse/QTMOBILITY-734 > Yes. You would need an api to tell the implementation that an > animation sequence is about to start so that the implementation could > turn optimizations for fast animations (not trying to load new tiles > on each zoom level change, or not to render text labels or other > expensive items on each frame). The app then would notify the > implementation that now animation has finished. That's exactly the idea. And it's got scope for a huge amount of tinkering and tweaking, so hopefully we get something basic going first before we get too carried away. Cheers, Dave _______________________________________________ Qt-mobility-feedback mailing list Qt-mobility-feedback@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
