Open jspitz opened 2 weeks ago
Ad 3. I have just learned that the fields that keep string constants need to be defined in prefs these days. Adding location
there solves this issue, although I think this definitely needs to be documented
The string editor problem persists.
@jspitz Try hitting enter after you enter the new String.
@jspitz Try hitting enter after you enter the new String.
Tried that, didn't work
Before you leave the field (after you entered the text), you have to hit enter
Hm, trying again, it does work. Don't know why I failed in the first place. So it's really all about documentation.
(or maybe make the UI a bit more accessible)
Glad it worked! Unfortunately we cannot fix this "commit cell value on enter" as it's a javafx problem but we will try to improve the UI and the docs
Glad it worked! Unfortunately we cannot fix this "commit cell value on enter" as it's a javafx problem but we will try to improve the UI and the docs
Refs https://github.com/JabRef/jabref-issue-melting-pot/issues/683
I don't know javafx
well, but you can you add two line edit widgets (for key and value, respectively) and an Add
button on top of the table? That's what I would go for, most probably.
JabRef version
5.15 (latest release)
Operating system
GNU / Linux
Details on version and operating system
JabRef 5.15--2024-07-10--1eb3493 Linux 6.11.6-2-default amd64 Java 21.0.2 JavaFX 22.0.1+7
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Trying to use
@String
constants with JabRef I am facing multiple challenges:@String{NewString = {}}
@String{ffm = {Frankfurt a.\,M.}}
) the string is correctly listed in the string editor. But if I want to use it in the location field as advised, namely#ffm#
, JabRef wrongly writeslocation = {#ffm#},
(rather thanlocation = ffm,
)#ffm#
; fine. But as soon as I change anything in this entry (say, fill in thelangid
field), the source changes back tolocation = {#ffm#},
(and the output is broken)Unless I have missed something, it looks like this feature is completely broken in this version.