-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Selecting an Entry preview style triggers an Uncaught Exception #7860
Comments
Refs. #7526 (comment) |
Mhm not sure. Which list exactly are you talking about? - Something within the edit field or the selected list? I can trigger the error pretty reliably in "selected" even when it is not empty, so not sure if the emptiness is a criterion. I can trigger it when selecting the styles via keyboard arrows and also when selecting them via mouse. I also get the error basically every time i click on customized preview style, but not always. Sometimes something seems to reset itself, i mean i guess that is to be expected, since the error message shows index issues. JabRef 5.4--2021-08-21--644e48d |
JabRef 5.4-PullRequest8110.247--2021-10-01--9bc899a Whereas in the older version (JabRef 5.4--2021-08-21--644e48d) prior to you having implemented the preview and edit function, the Available list did not trigger the error, now in the new version (JabRef 5.4-PullRequest8110.247--2021-10-01--9bc899a) it also triggers the error. |
This bug is unfortunately coming from an external library, seems like it's FXMisc/RichTextFX#1021 |
Hey guys, sorry I didn't see this earlier otherwise I would have tried to publish a RichTextFX update sooner. Anyways version |
The uncaught exceptions do indeed not trigger anymore in JabRef 5.4--2021-11-08--1eaaf50 and they also did not trigger in the development version from yesterday. Awesome! |
JabRef 5.4--2021-11-08--1eaaf50 Confirmed. Great news. Thank you! |
JabRef 5.3--2021-06-28--9fe7617
Linux 5.4.0-77-generic amd64
Java 16.0.1
JavaFX 16+8
Following on from #7652 :
Steps to reproduce the behavior:
The event log is empty.
Log File
The text was updated successfully, but these errors were encountered: