When saving a kst session the fileRelative paths for the data files are always saved relative to the current working directory rather than relative to the kst session file itself. When kst is started from the start menu the current working directory is the directory in which the kst bin directory is located and does not change when the kst session file is saved. When kst is started by double clicking on a kst session file the current working directory is the same as the kst session file so all fileRelative paths appear to be relative to the kst session file. Reproducible: Always Steps to Reproduce: 1. Start Kst from icon in start menu 2. Save empty session in same directory as data file 3. Import data file using wizard or any other method 4. Save session again Actual Results: If I have a data file located at "C:\David\Visualisation\KST Tests\formatted date times\data1.csv" and then save a kst session file that uses that data as "C:\David\Visualisation\KST Tests\formatted date times\kst.kst" then the fileRelative path is stored as "../../David/Visualisation/KST Tests/formatted date times/data1.csv". This means that if you move the files (session & data) to another location or transfer to another computer then the relative path is incorrect and when the session is loaded the user gets prompted that Kst cannot find the files and they need to locate the correct path. Expected Results: I would have expected the fileRelative path to be stored as "data1.csv", meaning that the data is relative to the kst session file and that moving those files together would still allow them to be found. Running binary release of Kst 2.0.7 under Windows 7 Pro x64 installed in "C:\Program Files (x86)\kst 2.0.7".
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!
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!
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!
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!
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!