[Kst] extragear/graphics/kst

[Barth Netterfield]

I'm not completely certain that we are doing the 'right thing' here, but here 
is the argument:

This behavior is required for count from end (start on a frame N*Skip where N 
is an integer).
I would like how a given frame range looks to be independent of the starting 
frame.  So we do the same thing for all modes.
I can see times where one would or would not want this.  If there is any 
consensus, I would be willing to have it changed (for everything except count 
from end).  

cbn

On Friday 20 October 2006 03:13, Brisset, Nicolas wrote:
> > SVN commit 596909 by treat:
> >
> > *Modify testcases as per barth.
> > *Refactor rvector to pass tests and clean up the source code
>
> I've just tested this with a series.dat file generated with:
> gawk 'BEGIN {for(i=0;i<=100;i++) print i}' > series.dat
>
> Using that file with the "Change data sample ranges" tool and the "View
> vector values" dialog, I have conducted a few "experiments". From what I
> tested it seems quite fine, the only case I find disturbing is if you
> select read to end, start frame = 2 and read 1 sample per 3 frames (for
> example) the first value in the resulting vector is "3" (which is the
> 4th sample). I expected "2" instead. From what I could tell the
> alignment on skip boundaries is also done in that case, so that
> sometimes you get the "right" first sample and sometimes not... Probably
> not a major issue but may lead to problems...
>
> Nicolas
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst