You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sdef editor has trouble with some sdef files that use newer xml elements (see man 5 sdef).
Worse, though, is that even if one edits a part of the sdef structure that's not using the unknown items, it will still erase them when saving the sdef file.
It would be nice if the editor would only modify the xml structure where it's being edited, without trying to reconstruct everything, thereby losing data it couldn't parse when loading it.
Even better it would be if it would handle all the new items.
(Update) I was under the impression that sdef had several iterations, adding more features later. It seems now that I was wrong. The last edits to the sdef format seem to be older than what the editor is based on.
So I guess I better list specific issues here. Once I run into a case where Sdef Editor reports issues opening an sdef file, I'll add it here.
The text was updated successfully, but these errors were encountered:
/System/Library/ScriptingDefinitions/CocoaStandard.sdef - does not like <access-group identifier="*"/>
/System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/Resources/StandardAdditions.sdef - does not like multiple types: <type list="yes"><type type="text"/><type type="number"/></type>
Sdef editor has trouble with some sdef files that use newer xml elements (see
man 5 sdef
).Worse, though, is that even if one edits a part of the sdef structure that's not using the unknown items, it will still erase them when saving the sdef file.
It would be nice if the editor would only modify the xml structure where it's being edited, without trying to reconstruct everything, thereby losing data it couldn't parse when loading it.
Even better it would be if it would handle all the new items.
(Update) I was under the impression that sdef had several iterations, adding more features later. It seems now that I was wrong. The last edits to the sdef format seem to be older than what the editor is based on.
So I guess I better list specific issues here. Once I run into a case where Sdef Editor reports issues opening an sdef file, I'll add it here.
The text was updated successfully, but these errors were encountered: