Bug 403608

Summary:	SaveAs defaults to "wrong" file path
Product:	[Applications] kmymoney	Reporter:	JAH <vanquestor>
Component:	file	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	5.0.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:	https://commits.kde.org/kmymoney/6f793d892d70b3934d15c876c7e741b2567694e4	Version Fixed In:	5.0.3

Description JAH 2019-01-25 22:36:52 UTC

SUMMARY:
When using "File > SaveAs" the offered path defaults to the last location a file was saved to even if that path has nothing to do with origins of the currently open file.

STEPS TO REPRODUCE
1. Open file /home/Jack/MyCash1.kmy
2. Save file
3. Open file /home/Dad/PaCash2.kmy
4. Use File > SaveAs 

OBSERVED RESULT
The SaveAs path defaults to /home/Jack/

EXPECTED RESULT
The SaveAs path should default to /home/Dad/ (which is the origin of the currently open file and the standard GUI behaviour).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Opensuse 15.1 with Plasma 5
(available in About System)
KDE Plasma Version: 5.12.6
KDE Frameworks Version: 5.45.0
Qt Version: 5.9.4.

ADDITIONAL INFORMATION
This exceptional behaviour is contrary to standard behaviour of SaveAs in other desktop applications and consequently makes it easy to inadvertently write the file to the wrong location (potentially overwriting identically named files irrevocably).

Comment 1 Thomas Baumgart 2019-01-26 15:25:20 UTC

Git commit 6f793d892d70b3934d15c876c7e741b2567694e4 by Thomas Baumgart.
Committed on 26/01/2019 at 14:10.
Pushed by tbaumgart into branch '5.0'.

Update last used directory when opening a file
FIXED-IN: 5.0.3

M  +3    -0    kmymoney/plugins/xml/xmlstorage.cpp

https://commits.kde.org/kmymoney/6f793d892d70b3934d15c876c7e741b2567694e4

Comment 2 JAH 2019-01-26 18:54:42 UTC

Thank you for such a prompt fix to this excellent application. I'm grateful for the time and dedication the team put into maintaining and developing it and have donated via KDE accordingly.

Comment 3 JAH 2020-03-05 19:05:12 UTC

*** Bug 335804 has been marked as a duplicate of this bug. ***