Bug 396852

Summary:	-x command-line option is ignored when attempting to specify source of X axis data
Product:	[Applications] kst	Reporter:	Jim Henderson <jim.henderson>
Component:	documentation	Assignee:	Philip Rodrigues <phil>
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/Implemented In:
Sentry Crash Report:
Attachments:	Dataset illustrating problem

Description Jim Henderson 2018-07-25 17:32:00 UTC

Launching Kst with command-line option    -x field-code  
The option is apparently ignored and consequently kst renders the data corresponding to  field-code  in the dataset on an independent graph, rather than using it as the reference for Y channel data as desired.  

Kst version details: 
Kst Kst-2.0.x-2018.06.20-08.35 Revision 39b8a6c37ac9b41528a3e648bff52a461543d8f9

Comment 1 Jim Henderson 2018-07-25 18:44:14 UTC

Created attachment 114123 [details]
Dataset illustrating problem

Comment 2 Netterfield 2018-08-29 18:21:57 UTC

What command line are you using?

The correct thing would be

kst2 <dirfilename> [frame range options] -x <xfield> -y <yfield>

To make the command line more powerful, order matters.

The -x has to come before the -y, but after the dirfile name and the frame range options.  This is to allow tricky things like

kst2 data.dir -f 0 -n 100 -x fieldX1 -y fieldY1 -x fieldX2 -y fieldY2

for example.

Comment 3 Netterfield 2018-09-21 14:06:51 UTC

If the instructions below do not work, please send the command line options you are using, and feel free to re-open the bug if it has been closed.

Comment 4 Andrew Crouthamel 2018-10-07 04:29:02 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 5 Andrew Crouthamel 2018-11-06 14:46:44 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!