I've just seen that a major new version has been released.

Will the bug we've identified be fixed in version 3.5x or will fixes only be done in the new version 4.x?

I've also noticed there's a new function called IsNewPixelPosition within FastLine.cs My guess is that the method used to determine which pixels are drawn for a given x , y at the given chart / screen resolution has changed. I thought to begin with that a function linking each of the pixels together...

I have found that it's caused by FastLine.DrawAllPoints being set to false. It's always been set this way. I assumed it worked out which points needed to be drawn depending on the resolution and this helped with performance. This is the first time we've seen a change in the behaviour. I'm still inve...

I've just updated the source from the version released on 23rd September 2008 to the latest version. It was a fairly smooth update but there seems to be a change in how the FastLine series is being rendered. It may well be a new feature / property that's been added that I need to change. It's causin...