Thank you, Mike.
On Wednesday 09 January 2008 04:36:21 pm Michael Droettboom wrote:
> I have something that works in r4833. It requires a clean rebuild,
> since the change was only to a header file. It produces no measurable
> slowdown on my fps test. (Of course, Eric's suggestion probably
> wo
I have something that works in r4833. It requires a clean rebuild,
since the change was only to a header file. It produces no measurable
slowdown on my fps test. (Of course, Eric's suggestion probably
wouldn't have either...)
Please let me know how this works for you.
The nice thing about t
I think this is an oversight on my part when doing the rewrite. The old
trunk had special code to deal with NaNs in draw_lines (in some
backends, but not all). Since draw_lines disappeared (it was replaced
with draw_path), this functionality fell through the cracks. I think
somehow bringing
Darren Dale wrote:
> It looks like the new transforms codebase does not support data that contains
> NaNs the way the old trunk did:
>
> plot([1,2,NaN,4,5]) produces a plot with no line break
> plot([NaN,2,3,4,5]) produces a plot with no line
>
> I know use of NaN's is not encouraged, and we hav
It looks like the new transforms codebase does not support data that contains
NaNs the way the old trunk did:
plot([1,2,NaN,4,5]) produces a plot with no line break
plot([NaN,2,3,4,5]) produces a plot with no line
I know use of NaN's is not encouraged, and we have discussed it on this list.
But
