Closed rksm closed 6 years ago
This is a problem that occurs when a layout's properties are deserialized in an invalid order. In that concrete case, spacing is deserialized before container is set, so the relayout that is triggered by the set of spacing crashes. Is there a way to define order of properties for plain lively classes aka static get properties() in morphs?
So b4ace7ae2e42199 puts a convention into place that was already present in other layouts, where the apply would be canceled in case the container is not set yet. however ordering property initialization remains the more elegant solution.
@merryman
due to style-widgets branch merge:
To reproduce: world menu => load world,
Error: