ASE Home Page Products Download Purchase Support About ASE
ChartDirector General
 Forum HomeForum Home   SearchSearch

Message ListMessage List     Post MessagePost Message

  Google Chrome
Posted by Kurt Wilde on Apr-30-2014 05:33
| Reply | Monitor
I noticed an issue with Google Chrome when positioning the mouse cursor.  When drawing the verticle line and starting at 0, in IE the line starts at the top of the chart.  However when viewing with Chrome, it starts quite a ways down.  Am I the only one to notice this?  Is there a work around or fix?  Thanks.

Kurt

  Re: Google Chrome
Posted by Peter Kwan on May-01-2014 03:19
| Reply | Monitor
Hi Kurt,

Is it possible to provide some sample code that can demonstrate the problem? There is
some track line examples in our web site, and in our testing, the "vertical line" is in the
correct position no matter IE, FireFox or Chrome is used.

http://www.advsofteng.com/gallery_track.html

Regards
Peter Kwan

  Re: Google Chrome
Posted by Kurt Wilde on May-01-2014 03:32
| Reply | Monitor
This seems to be the offending line:

var t = document.getElementById('<%=Chart1.ClientID%>').clientTop;
var h = document.getElementById('<%=Chart1.ClientID%>').clientHeight;
viewer.drawVLine("trackLine", xCoor, t,h, "blue 2px solid");

setting t to -70 starts the line at the top of the graph.

Chrome version 34.0.  Works fine in Firefox and IE.

  Re: Google Chrome
Posted by Peter Kwan on May-01-2014 04:48
| Reply | Monitor
Hi Kurt,

I have applied your code in the ChartDirector "Zooming and Scrolling with Track Line" sample
code, and it works normally in IE, FireFox and Chrome.

For your case, is it possible to create an example (such as by modifying the sample code)
to help me reproduce the problem?

I suspect the issue is related and triggered to some unique structure of your web page. The
web page structure can be because of your own code, or it can be generated by other third
party components or AJAX frameworks you may be using. To trouble-shoot the problem, you
may try to simplify your web page to the simplest possible (using all hard coded data so it
can be run standalone without connecting to a database). This can often help to determine
which structure can trigger the problem.

Regards
Peter Kwan