cutting-room-floor / easey-dead Goto Github PK

Right now optimal takes 3 arguments - 2 magic numbers (v and rho... awful names, but that's another issue) and a callback. The most common case will be providing a custom callback, which requires users to know the magic numbers. This should be fixed up.

Is there a way to use Easey with latest version of Mapbox.js (v1.6.0) (using mapbox map objects) ?

Cheers,
Antoine

Easey should map.dispatchCallback('zoomed') when zoom level changes.

Which BSD license is it under? The 3 clause version used for other Mapbox projects?

DragHandler behavior was changed in #14

I can't test, but it looks like the current TouchHandler has the same dragging behavior as the old DragHandler, where the location under the touch won't stay the same.

I looks like the transitions don't complete in IE 8. Tested on http://gop.sites.devseed.com

do it

The callback should not be required. It should work properly if called when nothing is running.

Load the page, interactivity working. Zoom in/out, still works. Drag the map, it stops working and mouse pointer is stuck on "grab" icon. Using Wax 4.1.8 and Modest Maps 0.20.0.

Implementation consists of these and nothing else:
new easey.DragHandler(),
new easey.TouchHandler(),
new easey.DoubleClickHandler(),
new easey.MouseWheelHandler()

It seems the touchHandler isn't working with android.

Support tickets:
http://support.mapbox.com/discussions/general-questions/3300-mapboxjs-support-for-touch-screen-devices
http://support.mapbox.com/discussions/mapbox-tiles/397-no-panning-on-android-with-mapboxjs-api

See this example. The code that did correct handling of .precise() has been lost at some point.

It just pops from location to location.

the code seems to zoom instantly into a random area of the world; it probably needs a double-tap to work correctly here.