Jason Winning

I downloaded Nextcloud and tried reproducing the issue. If Nextcloud is in the middle of syncing the XML files, and I click "Save to XML", I get an "Access Denied" popup 100% of the time. Basically, Nextcloud (unlike other sync services like Dropbox or OneDrive) locks files and prevents overwriting-by-renaming when it is in the middle of syncing. Hypernomicon writes temporary files and renames them in bulk in one operation when saving to ensure the XML files either all succeed or fail together (in...

You're right, it should be showing multiple rows when there are multiple targets of an argument. I will make it work that way for the next version. This isn't really an updating issue; currently it just never shows more than one row per argument record. It just shows you the first target in the list of targets for that argument.

I think I figured out why it was getting cut off. Are you continuing to see the Access Denied error?

Argument Name Suggestion Suggestion

I have committed this change to github. It will be in the next version.

The problem with having it automatically check/uncheck the checkbox is that it wouldn't work for users who use title case (capitalize every word) for their position/argument names. I think a better solution would be: If there is a word that matches a person record search keyword, don't change the capitalization of that word even if the "Lower case target name" is checked. I think that would give you the behavior you want, letting people set the checkbox and forget it for the most part. I think that...

The problem with having it automatically check/uncheck the checkbox is that it wouldn't work for users who use title case (capitalize every word) for their position/argument names. I think a better solution would be: If there is a word that matches a person record search keyword, don't change the capitalization of that word even if the "Lower case target name" is checked. I think that would give you the behavior you want, letting people set the checkbox and forget it for the most part. I think that...

The problem with having it automatically check/uncheck the checkbox is that it wouldn't work for users who use title case (capitalize every word) for their position/argument names. I think a better solution would be: If there is a word that matches a person record search keyword, don't change the capitalization of that word even if the "Lower case target name" is checked. I think that would give you the behavior you want, letting people set the checkbox and forget it for the most part. I think that...