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
Over time the file format changed little by little. e.g. geometric shapes like rectangles or ellipses introduced an attribute for hatch style at some point. During parsing it's important to know with which file version we interact as there is e.g. a hatch attribute stored or not.
I searched for it a while but don't even have an idea which value (offset) could be considered. The amount of files does not make it much simpler, probably the version is not saved in the actual symbol file itself as I have searched it pretty thoroughly but rather in a centralized file.
The text was updated successfully, but these errors were encountered:
Over time the file format changed little by little. e.g. geometric shapes like rectangles or ellipses introduced an attribute for hatch style at some point. During parsing it's important to know with which file version we interact as there is e.g. a hatch attribute stored or not.
I searched for it a while but don't even have an idea which value (offset) could be considered. The amount of files does not make it much simpler, probably the version is not saved in the actual symbol file itself as I have searched it pretty thoroughly but rather in a centralized file.
The text was updated successfully, but these errors were encountered: