I am a bit confused about add/remove vs. show/hide columns in the requirement of Right-click menu for the main table header. I understand that the past group have done is confused since now they have 2 ways to show/hide the column in the maintable: By changing the columns in the preferences AND also by showing/hiding them in the right-click menu. My understanding is you want to add/remove a column or a set of columns (maybe commonly used columns) that are different from these columns already shown in the main table? Could someone please clarify it for me? Thank you very much!
@Yancy10-1: When I asked Carl about causes for Index out of bounds error he mentioned this: "I am not an expert for this, but I know that this often indicates a problem with threading / concurrency. Especially between UI thread and others.
It can be problematic when trying to add or remove individual items in a list in another thread, when that list is not in the same thread. The solution can be to use concurrency-safe methods to populate a list (e.g. setAll) or multithreading-safe lists. This is not the default in Java and Java-lists (because performance), but you have to consider it during development."
Translated with www.DeepL.com/Translator (free version)
For methods about preventing index out of bounds issues, he refered me to these two websites:
https://www.baeldung.com/java-concurrency
https://www.baeldung.com/java-thread-safety
1 reply
Found
- https://github.com/arturssmirnovs/random-github-issue
- https://arturssmirnovs.github.io/random-github-issue/
Maybe it could be forked and adapted to only find issues in JabRef.
Solution (please refer to image below):
I have planned to run a loop to remove selected groups instead of just remove the only group that fire setOnAction().
Issue with this solution:
If a group has been deleted, the iterator will skip the next element due to that element is now at that deleted element index. Refer (https://stackoverflow.com/questions/17852412/foreach-skips-an-element-when-a-previous-element-is-deleted)
Really appreciate if someone could provide insight to this issue, thanks!
Hello everyone! My team is working on this JabRef/jabref#8762 and we are wondering if you had any suggestions (functions) for adding a column to the mainTable. (or which class / function is used to add columns in Preferences /Entry Table)
We have found a way to remove the column from the MainTable (which also removes it from the preferences/entry table) using a context menu we created (removing it just by comparing the names of the column in our context menu with the maintable when a user clicks an item from our context menu)
Anoop, there are different entry types. E.g. Article, book, misc or patent (see screenshot).
For each entry type there are specific fields REQUIRED and some OPTIONAL, as defined by BibTeX and BibLaTeX. JabRef follows these standards and offers two specific library modes by default: BibTeX library mode and BibLaTeX library mode. The required and optional fields CHANGE when you change the library mode.
As I understand it, all custom fields that users manually add to their library and that are NOT defined in these required and optional fields under options > customize entry types will currently show in the other fields tab.
About the code: I don't know exactly which classes and methods deal with that, but since you deleted some, I guess experimenting a little will eventually show you.
At the end of the day: It is not wanted to get rid of the various entry types. The task is NOT to get rid of these fields. The task is simply to let all the fields that are not part of an entry type to also show in the optional fields tab, but in a separate section (Maybe with title "Other fields" and/or separate colour/icon.
Anoop, there are different entry types. E.g. Article, book, misc or patent (see screenshot).
For each entry type there are specific fields REQUIRED and some OPTIONAL, as defined by BibTeX and BibLaTeX. JabRef follows these standards and offers two specific library modes by default: BibTeX library mode and BibLaTeX library mode. The required and optional fields CHANGE when you change the library mode.
As I understand it, all custom fields that users manually add to their library and that are NOT defined in these required and optional fields under
options > customize entry typeswill currently show in theother fieldstab.About the code: I don't know exactly which classes and methods deal with that, but since you deleted some, I guess experimenting a little will eventually show you.
At the end of the day: It is not wanted to get rid of the various entry types. The task is NOT to get rid of these fields. The task is simply to let all the fields that are not part of an entry type to also show in the optional fields tab, but in a separate section (Maybe with title "Other fields" and/or separate colour/icon.
Thanks
1 reply
