You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My app uses very large numbers of events (well over what is recommended) and is focused on delivering lots of information about the event located at the custom time:
Your description of the zoom behavior is correct (point 1 and 2). The zoom behavior is similar to that of Google Maps, and is indeed not configurable. I strongly doubt whether it is a good idea to change this zoom behavior and mess with users navigation expectations/habits.
Maybe you should look in a different direction to find a good way to navigate your data around the custom time? What about having a small menu on top of the timeline, with shortcuts to move the visible range to the mostly used ranges? Something like:
Show: Current day, Current week, Current month, Current Year
in which the links will move the Timeline such that the custom time is in the center, and zoomed to the appropriate level.
A completely different solution would be to put an event listener on the rangechange and rangechanged events, and when the Timeline is moved/zoomed by the user, change the custom time such that it stays in the center of the currently visible area. Another event listener can listen for the timechanged event (triggered when the user has dragged the Custom Time bar), and adjust the visible area again such that the custom time stays in the center again. Nicest is of course to do the latter in an animated way (see example21).
My app uses very large numbers of events (well over what is recommended) and is focused on delivering lots of information about the event located at the custom time:
http://ifcb-data.whoi.edu/mvco
However zoomability doesn't seem to be configurable to allow me to use the custom time as the zoom center. Rather I see the following behavior:
Is there an option to use the custom time as the zoom center or is that a missing feature?
The text was updated successfully, but these errors were encountered: