-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"New file link" opens wrong folder in FileDialog #1609
Comments
I will try to work on this in the next days. See #1336 |
Fix for JabRef#1609 TODO: Investigate BrowseAction usage in FileListEntryEditor
On a first glance it does not open the intended directory but requires a further click on the "browse" button to open the link. This is a different behaviour as before. Actually I prefer when the link is opened. I have installed: JabRef_windows-x64_3_6dev--snapshot--2016-08-10--master--8342956.exe |
I rechecked the code and you are partly right.
Edit:// I described both cases here, because it's the same code and dialog that is used in both cases |
Please test again with the version from here: |
I tested it with that version. It works. However I experienced repeatingly file save issues: The first time an entry was cut before I was fully saved, interestingly the same entry was completely saved just after that faulty saved one. The next time, there were three entries not completely saved, however the completely entries were just behind. (Detected by editing the file with Notepad++). The error is in the save process and is not detected by Jabref itself, only by running biber on this file. |
@bernhard-kleine Thanks for your feedback. Would you please open a new issues for this and provide some steps for reproducing? As many details as possible. That helps us to track the error/faulty save process. |
Refactored Open and Save dialogs Introduced FileExtensions enum for FileDialog Filter Updated BrowseAction to use new dialogs Fix JabRef#1324 Fix JabRef#1609
JabRef version 3.5 and current 3.6dev on Windows 10
Steps to reproduce:
Reported by @bkleine in the discourse forum
The text was updated successfully, but these errors were encountered: