sangltdn / flot

Automatically exported from code.google.com/p/flot
MIT License
0 stars 0 forks source link

maximum defined, results in corrupted graph for values over max #229

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I don't konw if bug 210 might indicate the same issue. From the examples
page I modified the overview example with time.

yaxis: { ticks: [], min: 0, max: 4000 },

Now for all my values over 4000 I got output artifacts with a horizontal
line to the vertical axis at the origin. Removing the limitation solved the
issue.

Original issue reported on code.google.com by ste...@konink.de on 4 Oct 2009 at 1:33

GoogleCodeExporter commented 9 years ago
Hi. I read your explanation a couple of times, and it sounds like it might be a 
bug
in the clipping code. Or maybe something else. Would you mind trying with the 
latest
SVN version?

You need excanvas.min.js and jquery.flot.js from here:
http://flot.googlecode.com/svn/trunk/

Otherwise you need to attach a small but complete example so I can reproduce it.

Original comment by olau%iol...@gtempaccount.com on 21 Oct 2009 at 7:30

GoogleCodeExporter commented 9 years ago
Sorry to say, but SVN is even worse.

http://monitor.openstreetmap.nl/

Is the app; I changed options. As you can also see there when you horizontally 
resize
the window the labels go mad.

Original comment by ste...@konink.de on 21 Oct 2009 at 8:00

GoogleCodeExporter commented 9 years ago
Not worse; you can close this bug. The horizontal label stuff is still going on.

Original comment by ste...@konink.de on 21 Oct 2009 at 8:07

GoogleCodeExporter commented 9 years ago
OK, great. I think you need to remove the y axis labels on your overview graph. 
You
can do it with something like yaxis: { labelFormatter: function () { return ""; 
}}.
To make them both line up, you can set labelWidth to something reasonable on the
yaxis on both.

Original comment by olau%iol...@gtempaccount.com on 21 Oct 2009 at 8:33

GoogleCodeExporter commented 9 years ago
Jup that is tuning; regarding to the moving labels on resize; is that a bug in 
this
list or should i mention it somewhere?

[as side note; I think it would be really sweet if a 'loading' bar could be
implemented; but that is clearly an enhancement]

Original comment by ste...@konink.de on 21 Oct 2009 at 8:39

GoogleCodeExporter commented 9 years ago
Moving labels: you need to fix the width of the chart. Flot is drawing an 
image, so
it's not really resizable without redrawing. You can also listen for resize 
events on
the div and replot I think (I have not tried it myself).

Loading: best suggestion is put a div up, do the plot, then remove it again. The
plotting itself is synchronous, so although the browser is probably still doing 
a
couple of things in the background when you get back from $.plot, I think it's 
a good
enough approximation. Often people want to retrieve data as part of the plot, 
so I'm
not really sure it's that useful to stick to functionality inside Flot itself.

Hope this helps. :)

Original comment by olau%iol...@gtempaccount.com on 22 Oct 2009 at 1:19

GoogleCodeExporter commented 9 years ago

Original comment by dnsch...@gmail.com on 4 Jun 2012 at 2:52