tmtron commented on issue #15775: URL: https://github.com/apache/echarts/issues/15775#issuecomment-996672925
> For example, when I click the `dataZoom`, what I expected is getting the `percent` of the point I clicked so I could do more things like move to this range, just like other events. That would for sure be good to have. I think, that you can always add additional data to the event without breaking backward-compatibility, right? e.g. adding `clickpointValue`, `clickpointPercent` properties >But I don't think clicking on the dataZoom area to fetch more data is an intuitive user interaction. Well, I don't know a better way to do this. However I am very open to suggestions. Some more info: - In a first version we had an external button and menu entry to `Load the selected zoom region` - but that was inconvenient and clicking on the zoom slider directly is much preferred by the users. - Later we auto-loaded the data after some time, but that was annoying to the users (and caused useless load on the server), so we deactivated this. - BTW: we also reload data when they click on a brush area > Especially when it having conflicts with our builtin user interaction that `click to select'. The selected window will be changed after I clicked the dataZoom. So what range should it use to fetch the data, the new one or the old one? In this case, we would reload the old-data region (i.e. we don't use this click to move-window feature at all). However, when you want full support for this, then the event should contain the old range and the new range. And maybe even let the user cancel your default action (i.e. move the window to the new range). >Also we can't provide any hint to users letting them know they can click the dataZoom to load more data now. Well, we don't need such an indication - and if this is desired, the application can work around that: e.g. we could show a modal help window when the users use the zoom slider/brush for the first time, etc. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
