Page 1 of 1

Zoom and Scroll Problem

Posted: Mon Jul 16, 2007 11:55 am
by 13045392
Hello,

I use 3. verision. I have some problems about webchart in my web application.
Fisrtly, how can I zoom custom axis? In your examples there are mouseUp , mouseDown, Zoom , UnZoome event but I could not find them in web application. I have to capture mouseDown point and mouseUp point. How can I do that to zoom on selected area on custom axis?
Secondly, Do scroll and zoom properties work together? If yes, How can I do that?

Thank you for spending your time.






I want to get coordinates of when mouseUp and mouseDown so I zoom this area.
How can I do that?

Posted: Mon Jul 16, 2007 1:26 pm
by Chris
Hello,
Fisrtly, how can I zoom custom axis? In your examples there are mouseUp , mouseDown, Zoom , UnZoome event but I could not find them in web application. I have to capture mouseDown point and mouseUp point. How can I do that to zoom on selected area on custom axis?
I believe the content of this question identical to the one you posted in the "SetCurrentZoom" thread below. I am presently looking into this question and will get back to you with an answer when I have one.
Secondly, Do scroll and zoom properties work together? If yes, How can I do that?
Again, I ask you please for your patience while I look into this issue and get back to you with an answer.

Posted: Mon Jul 16, 2007 3:26 pm
by Chris
Hello!
Fisrtly, how can I zoom custom axis? In your examples there are mouseUp , mouseDown, Zoom , UnZoome event but I could not find them in web application. I have to capture mouseDown point and mouseUp point. How can I do that to zoom on selected area on custom axis?
This is not possible using the WebChart as it is at the moment, however, I've made this issue a high priority feature request which means there is a good chance it will be included into the next maintenance release.
Secondly, Do scroll and zoom properties work together? If yes, How can I do that?
Again, this is not possibly using the current version of the WebChart. This issue is a now a feature request, which means that it will be included into a future maintenance release.