Separate path remembering for loading and saving nets
Bug #1855266 reported by
Jiri Srba
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| TAPAAL |
Fix Released
|
High
|
Peter Haahr Taankvist | ||
Bug Description
When you open a net in a directory and then try to save it (e.g. using export PNML and export Queries) then it will offer the directory where it opened the file the last time. Similarly,
if you save a file and try to open a new one, it will offer as default the directory where it
was saved. It would be nice to seperate these two paths, open for opening files (and importing pnml and queires) and one for saving files (and exporting pnml and queries, gifs, tikz etc).
Related branches
lp:~tapaal-contributor/tapaal/seperate-save-paths-1855266
- Jiri Srba: Approve
- Peter Haahr Taankvist (community): Needs Resubmitting
- Kenneth Yrke Jørgensen: Approve
-
Diff: 222 lines (+40/-23)4 files modifiedsrc/pipe/gui/GuiFrame.java (+4/-4)
src/pipe/gui/widgets/filebrowser/FileBrowser.java (+4/-6)
src/pipe/gui/widgets/filebrowser/NativeFileBrowser.java (+14/-6)
src/pipe/gui/widgets/filebrowser/NativeFileBrowserFallback.java (+18/-7)
Revision history for this message
| Kenneth Yrke Jørgensen (yrke) wrote | #1 |
| Changed in tapaal: | |
| status: | New → Fix Committed |
| Changed in tapaal: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
In general this separation is quite weak, there are some remains from supporting this trohugout the code, however over time it has degenerated and today quite confusing. I would suggest to remove the old parts completely before reimplementering the feature.