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
This is just an issue with those two demo artwork files. For context, whenever we break the file format, we have to manually go through all the demo artwork files and edit the JSON to upgrade the format.
You'll need to format it to be readable, in VS Code do Ctrl+Shift+P > "Format Document With" > JSON Language Features. Then make your edits. Then when it's all fixed, open the formatted file in Graphite and re-save it from Graphite to get the condensed formatting back so it's all on one line again.
For second issue (when grouping layers, it will split items to two folders):
Not all layer affected in the mentioned demo artwork. Only folders with its input[0](children) as a artboard_layer, rather than the desired ordinary_layer are affected.
It means undefined behaviors occur and no error-catching here:
Folders' input[0] as a artboard_layer. These problematic folders will become an empty layer once no ordinary_layer in it.
When 1 appears and doing "group into folder" or doing "resorting", all siblings are placed into a problematic folder again.
(Update) Is there any ways to create Folders' input[0] as a artboard_layer?
I didn't figure out.
However, the demo artwork's not-desired artboard_layer are all Transform, and by accessing the corresponding folder in both the top-right node graph and the layers widget window, you can find the properties not found in other folder.
In #1719 (comment), two weird behavior appeared in
Just a Potted Cactus
andValley of Spires
:Other two example artwork, newly (master branch) saved document didn't affected.
The text was updated successfully, but these errors were encountered: