Bug 302286 - Add an option to store only relative path in kst file
Summary: Add an option to store only relative path in kst file
Status: RESOLVED WORKSFORME
Alias: None
Product: kst
Classification: Applications
Component: general (show other bugs)
Version: 2.0.5
Platform: Microsoft Windows Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: kst
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-21 08:58 UTC by Grégoire Verlut
Modified: 2023-01-31 05:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grégoire Verlut 2012-06-21 08:58:54 UTC
I work a lot with "generic" kst file, that I generate once. When this template kst file is ready, I copy it to all the directory where I want to perform the analysis.

I really wnat to be sure that kst looks only in the current directory, and do not open file stored elsewhere.

Reproducible: Always

Steps to Reproduce:
1. create a kst file, where 2 data file are needed
2. move the kst file to another directory, where only one data file is present (the other is not present if the records failed for example)
3. open the moved kst file, 
Actual Results:  
kst will mix data file from the directory of point 2 (normal behavior) and directory of point 1 (for the file not found in point 1)

Expected Results:  
I would appreciate two options under "save as" for instance called "save with relative" and "save with absolute".
The "save with relative" will store for the "file" tag the same value as the "fileRelative"
The "save with absolute" will store for the "fileRelative" tag the same value as the "file"

Today, I edit the kst in an editor to get rid of these absolute reference :)
Comment 1 Andrew Crouthamel 2018-11-09 01:09:46 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-20 04:06:33 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-01 04:19:47 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-16 05:13:13 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
mark the bug 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 Bug Janitor Service 2023-01-31 05:05:28 UTC
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!