[kst] [Bug 396853] New: -n option ignored when using GetData data source containing float or double data fields

[Jim Henderson]

https://bugs.kde.org/show_bug.cgi?id=396853

Bug ID: 396853
Summary: -n option ignored when using GetData data source
containing float or double data fields
Product: kst
Version: 2.0.8
Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: plotting
Assignee: ***@kde.org
Reporter: ***@elkengineering.com
Target Milestone: ---

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.

[b***@kde.org]

https://bugs.kde.org/show_bug.cgi?id=396853

***@astro.utoronto.ca changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@astro.utoronto.
| |ca

--- Comment #1 from ***@astro.utoronto.ca ---
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.

[b***@kde.org]

https://bugs.kde.org/show_bug.cgi?id=396853

***@astro.utoronto.ca changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|REPORTED |NEEDSINFO

--- Comment #2 from ***@astro.utoronto.ca ---
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.

[Andrew Crouthamel]

https://bugs.kde.org/show_bug.cgi?id=396853

Andrew Crouthamel <***@kdemail.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |triaged

--- Comment #3 from Andrew Crouthamel <***@kdemail.net> ---
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!

[Andrew Crouthamel]

https://bugs.kde.org/show_bug.cgi?id=396853

Andrew Crouthamel <***@kdemail.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED

--- Comment #4 from Andrew Crouthamel <***@kdemail.net> ---
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!