Bug 396853

Summary:	-n option ignored when using GetData data source containing float or double data fields
Product:	[Applications] kst	Reporter:	Jim Henderson <jim.henderson>
Component:	plotting	Assignee:	kst
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	netterfield
Priority:	NOR	Keywords:	triaged
Version First Reported In:	2.0.8
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jim Henderson 2018-07-25 17:40:36 UTC

Launching kst with command-line option     -n 100  
The -n 100 argument appears to be ignored by KST when using GetData data sources.  If the data source is closed before launching KST, all data from all channels in the GetData source are rendered.  If the data source is open (and contains >= 100 data points) when launching KST, the resulting graphs are blank, showing no data in the set.

Comment 1 Netterfield 2018-08-29 18:32:21 UTC

What command line are you using.

The correct syntax would be

kst2 <datafile> -f 0 -n 100 -y field

That is, order matters, and the -f and -n entries must come before the -y.  This is to allow such tricky things as

kst2 datafile1 -f 0 -n 100 -x fieldx, -y fieldy -f 1000 -n 100 -x fieldx -y fieldy

to plot 2 different sections of data from the same command line.

let me know what syntax you were using on the command line.

Comment 2 Netterfield 2018-09-21 14:08:08 UTC

If the instruction below do not work for you, please send the exact command line options you are using.  Feel free to re-open the bug if it has been closed.

Comment 3 Andrew Crouthamel 2018-10-07 04:28:52 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Andrew Crouthamel 2018-11-06 14:46:52 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!