[Kst] getData flexibility

[Brisset, Nicolas]

> De : Barth Netterfield [mailto:netterfield at physics.utoronto.ca] 
> Envoyé : jeudi 4 mai 2006 02:39
> À : kst at kde.org
> Objet : Re: [Kst] getData flexibility
> 
> Your changes are fine - iff it doesn't give us a hit in 
> performance - but I'm not entirely sure they are critical....
> 
> I was thinking less ambitiously : in the comments below, I 
> indicate what I though was happen...
> [...]
I don't know how difficult implementing all this would be, but from a user's perspective I think NaNs are OK as long as no curve is drawn where the value is NaN (interpolation or keeping the last value and continuing the line would be very bad, but I don't think that's what happens).
I find the idea of greying out the part of a plot where data is not available quite cool, even though I'm not sure it requires frame ranges to implement. Why not just grey out areas where either the X vector or all Y vectors have NaNs ?

> > The problem stems from the fact that I can only return -1 for any 
> > error, so I can't signal a partial success very easily.
How about when readField returns a value lower than n (the requested number of frames) ? I thought that'd mean "partial success"...

And last point, I also think that we could save some memory by using something else than a double * for datasource data (I upcast floats 99% of the time in my case), but it may be difficult to implement, and maybe not worth the trouble with today's computers with a lot of RAM, and FPUs that work with doubles internally anyway (if I'm not mistaken) ?

Nicolas