[Kst] [Bug 94193] Read to End should use reqnframes not nframes

[Barth Netterfield]

I think an example of the idea is this:

You open a live data source with -n 1000, but when you open it, there are only 
100 frames in it.  You see all 100 frames, with the displayed range growing.  
If you did nothing, the range would keep expanding, until you see frames 0 - 
999, then things would start scrolling (1-1000, 2-1001, etc...)

But, when the file is only 500 frames long, you hit 'read from end'.  Now you 
start scrolling, limited to 500 frames (1-500, 2-5001, etc).

The correct behavior would have been to not change the requested number of 
frames, but to only set count from end (which was already set in this case).

This example is not a big deal, but if you have multiple data sources, etc, it 
could be.

On December 6, 2004 12:35 am, George Staikos wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=94193
>
>
>
>
> ------- Additional Comments From staikos kde org  2004-12-06 06:35 -------
> I don't understand.  Do you want the number of frames to be consistent,
> reading from the end?  If so, then that should be "Count from end".  If you
> want the starting frame to always be X, you should use "Read to end".  Is
> there something other than this that you want?
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst