Fixed missing trigger for linked file operations

[calixtus]

Fixes #7525

• Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (for UI changes)
• Checked documentation: Is the information available and up to date? If not created an issue at https://github.com/JabRef/user-documentation/issues or, even better, submitted a pull request to the documentation repository.

[tobiasdiez]

I was also looking at this, and got confused why there is a binding to the executable state in the first place. The context menu is created when the user right clicks the file, and then the state doesn't change until the user chooses a an option from the menu. Moreover, the linked file view model should be recreated as soon as the content of the file field changes - so no binding needed since the linkedfile is constant for all practical purposes. What I am missing?

[calixtus]

I have no idea, but it works... 😅

But seriously: The ContextAction command was introduced in the first place to prepare this for a later to be added undo functionality. I tried it also with BindingsHelper.constantOf() and directly with setExecutable() but this did not show a consistent behaviour, my guess is that something is still cached.

In this state I think it works, but some more investigation surely wouldn't hurt.

[tobiasdiez]

Yeah, I'm also afraid that it is actually a cache error and it still shows the context menu for the previous version of the linked file. Hopefully that doesn't lead to more problems, e.g. when the action is performed with respect to the previous version instead of the current one.