Closed 0000marcell closed 3 years ago
I'm not sure, you complained about invisible items, because designers wanted them.. now you want to remove the invisible items? 🤨 They are used as guides sometimes. What if you have an item 'inside' an invisible item? Shouldn't we just add that item to the inside of the invisible, and make the invisible just a transparent frame?
Invisible is different than transparent if you have a "node.visible == false" it means that the node and all their children are not visible in the canvas, the invisible toggle is that little eye in the elements tree, designers like to make items invisible so they can toggle the visibility and show different states of the element, let's say I have an input that has an error state, what I see often is that designers create two inputs that represent each state then use the eye to show the two states, but in our case when transforming the elements we don't want the invisible item, if we convert the invisible item in this case we going to have two inputs, it's also common to have garbage in the design, that the designers made it invisible and forgot to delete completely
You were absolutely right! I just added this in the most recent commit, with HTML support. The thing is, I added in the final steps of the parser, instead of the altConversion, so the altConversion can work even with invisible items (like use a background invisible rectangle as the parent, which some people do use).
Feel free to test! Thanks for the idea.
This is just what I mentioned in issue #9, I was going to put a option to ommit hidden elements in the UI, something like a checkoutbox, but I don't understand whats the point of converting the hidden elements in any situation so I'm just filtering out the invible elements, elements that have visible false