Red frames of bar graph using mouse track is broken

[GoogleCodeExporter]

If the x-axis position of first item doesn't start from 0, the red frames
of bar graph using mouse track will be broken.

Different start positions lead to different types of frame fragmentation.

flotr: newest "flotr-read-only" checked out by svn
OS: Debian, 2.6.32-trunk-686
Browser: Iceweasel 3.5.8

Original issue reported on code.google.com by Bafu.C...@gmail.com on 4 Mar 2010 at 4:03

Attachments:

• flotr_barframe_frag_1.png
• flotr_barframe_frag_2.png

[GoogleCodeExporter]

I got the same Problem with a "points"-Graph.
The red border dosen't fade after mouseout.

Original comment by jpenzko...@gmail.com on 14 Apr 2010 at 6:48

Attachments:

• flotr.jpg

[GoogleCodeExporter]

Attached is a very simple patch which I believe solves this issue for bar 
graphs.

The width calculation for the call to clearRect wasn't taking into account the 
actual value of the x-axis minimum.

Original:  xa.d2p(bw) + lw * 2
Patched:   xa.d2p(bw + xa.min) + lw * 2

Note, the width may also be calculated as follows... which I think is more 
clear, but if the patch is accepted I will leave it up to you to decide what 
you like better :)

(bw * xa.scale) + (lw * 2) 

Original comment by justin.r...@gmail.com on 27 Jun 2010 at 4:20

Attachments:

• flotr_bartrack.patch

[GoogleCodeExporter]

Thank you ! fixed in the next release (both for bars and points)

Original comment by fabien.menager on 16 Jul 2010 at 7:16

• Changed state: Fixed

[GoogleCodeExporter]

I am still facing the same issue even after above patch is applied. Whenever I 
track a bar i get a red frame after mouseout. Specially when I have -ve data in 
chart

Original comment by akm.14...@gmail.com on 24 Jan 2012 at 10:04

Attachments:

• bug.png