Modified database marker invisible

[crystalfp]

Running Windows 10 with the taskbar vertical on the right side of the screen.
When I modify a database, The JabRef taskbar icon puts the modified mark, the asterisk, at the end of the filename, making it invisible on the taskbar.

The fix is to put the asterisk at the beginning of the filename as, for example, Notepad++ does.

JabRef 4.3.1
Windows 10 10.0 amd64
Java 1.8.0_171

[tobiasdiez]

Can you please add a screenshot that shows your problem. I'm a bit confused how the asterisk that JabRef adds to the library name depends on the Windows taskbar.

[crystalfp]

Here they are. The first screenshot shows JabRef with the References.bib file modified. The asterisk is not visible in the taskbar on the right. Instead Notepad++ clearly show that the file has been modified in the taskbar icon.

If I hover the icon the window title is visible and the asterisk is present, just in a position that makes it not useful.

Hope now it is clear. For me it is a malfunction (something that does not carry to the user the status).
Thanks for your help and your useful tool!
mario

[stefan-kolb]

This might be worth a consideration.
However, we need to check how this behaves with multiple open tabs.
Also, just for clarification this is no standard behavior and is also not inplemented by other editors like Atom or Sublime (as far as I can see).

[crystalfp]

Yes I know there is no standard here, just convenience. With the editor (btw, I tried and removed Atom and Sublime moving to np++ and VS Code also for this reason) I notice if I modified something, with JabRef I have to activate it and check. For multiple tabs only the active one should show the modified status.
Anyway, thanks for looking at it!
mario

[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!