View Single Post
Old 09-28-2023, 04:47 PM   #181
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,904
Karma: 6120478
Join Date: Nov 2009
Device: many
@Vanguard3000,

Thanks for your bug report. I am not sure what exactly you mean be Properties here (versus Elements in the Metadata Editor).

I tried removing all elements (and of course all of their Propterties) and saw no problems. It all worked.

I tried removing all Elements then adding in the Author Element (dc:creator with role set to author). Then tried removing just the Author Name field and no problems.

Finally, I removed all Elements and then added back Author and removed both the role property so all I had was a blank dc:creator element with no properties, and saved that with no problems.

So would you please give a specific example and tell me exactly what to delete or remove to cause the crash, as having no properties on an element, and having no elements, both worked just fine for me.

So I must not be following exactly how to create the crash.

Thanks!


Quote:
Originally Posted by Vanguard3000 View Post
Found a new bug for you, which is pretty minor but hopefully also a quick fix.

Basically, if you go to the Metadata Editor and remove all Properties and hit OK you'll get a hard crash. It doesn't seem to be an issue with removing any specific Property; it's only if you try and commit with no Properties. This is pretty easily reproduceable and happens every time you follow the steps provided.

At the moment, I'm using the "2.0.1" test build KevinH provided to address the dual monitor issues I had been having with 2.0.0.

I would imagine the fix would involve a null check and/or ensuring there's some basic info in the metadata (i.e. last modified date), or at the very least the OK button should be disabled (or trigger an error) if the metadata is empty.
KevinH is online now   Reply With Quote