On Linux some JavaFX tables are "lazily" updated

[systemoperator]

I am using the latest JabRef 5 master build:
on Ubuntu 16.04

Some JavaFX tables get "lazily" updated on Linux: In more detail, e.g. the table in the dialog "Manage external file types" (Options > Preferences > External programs > Manage external file types) is only refreshed, when an updated entry firstly gets scrolled out of the visible table area and then gets scrolled back in, so that the table entry is again visible, then also the values contained in this changed entry are actually shown updated.

[tobiasdiez]

Does this apply only to this particular table, or do you see the same behavior also in other dialogs?

[Siedlerchr]

Regarding the manage external file type dialog: Maybe you need to add the Extractor property, so that underlying changes are properly reported:

 private ObservableList<FieldViewModel> fieldsForType = FXCollections.observableArrayList(extractor -> new Observable[] {extractor.fieldNameProperty(), extractor.fieldTypeProperty()});

I needed this in the custom external file types dlg as well

https://www.jensd.de/wordpress/?p=1650

[systemoperator]

@Siedlerchr I don't think, this will help, since even if I remove an entry in the list and I add a new one, the table is not getting refreshed, although this should update the table, as described in your link.

(Btw: I have already seen the pattern list.remove(POJO); list.add(POJO); in JabRef and until now I was just wondered why. Now I know. ^^)

[systemoperator]

Currently, I could only observe it in this particular table. In the main table, I could observe a different behavior, for which I will create different issues.

[systemoperator]

Nevertheless, I tried the suggestion of @Siedlerchr but it did not help.

[github-actions]

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

• If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
• Provide further steps or information on how to reproduce this issue.
• Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
• If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

[systemoperator]

Issue still persists. Description has been updated.

[github-actions]

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

• If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
• Provide further steps or information on how to reproduce this issue.
• Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
• If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!