Skip to content
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

Erratic behavior when clicking on "Get fulltext" #2391

Closed
avaucher opened this issue Dec 17, 2016 · 2 comments
Closed

Erratic behavior when clicking on "Get fulltext" #2391

avaucher opened this issue Dec 17, 2016 · 2 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs

Comments

@avaucher
Copy link
Contributor

JabRef development version on Linux (and probably other platforms)

In some cases, the behavior when clicking on "Get fulltext" is erratic or, at least, unexpected and/or misleading.
Two cases are explained below.

Steps to reproduce:

First, in "File -> Database properties", set "General file directory" to the directory with your files to link.

Case A: When multiple entries are selected.

  1. Have two bibtex entries with Bibtexkeys "a" and "b"
  2. Create corresponding files "a.pdf" and "b.pdf" in the directory chosen before.
  3. Double-click on "a" to select it and show the editor view
  4. In the editor view, go to the "General" tab.
  5. With Ctrl, click on the entry "b" so that both "a" and "b" are selected, and the editor view still shows entry "a"
  6. Click on "Get fulltext"

Result: Both "a.pdf" and "b.pdf" are added to entry "a" !!

Case B: When adding an entry after performing a search.

  1. Create corresponding files "a.pdf" and "b.pdf" in the directory chosen before.
  2. Have a bibtex entries with Bibtexkeys "a", containing the text "AAA"
  3. Select entry "a"
  4. Perform a search for "AAA". Only the entries containing "AAA" are listed.
  5. Create a new entry. In the editor view, give it the bibtexkey "b"
  6. Under the "General" tab, click on "Get fulltext"

Result: Instead of linking the file "b.pdf", it will link the file "a.pdf" !!

@koppor
Copy link
Member

koppor commented Dec 17, 2016

When #2270 is solved, this issue also gets solved - at least Case B. A probably not.

@koppor
Copy link
Member

koppor commented Dec 17, 2016

The fix provided by @avaucher at #2392 also provides a solution, which works, because the action of the button is local to the entry editor.

@koppor koppor closed this as completed Dec 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs
Projects
None yet
Development

No branches or pull requests

3 participants