I was creating a uxml template from another uxml. After removing elements from the original uxml, I saved what remained as another uxml. I open the original uxml and it was the same as the template I had saved after removing the unneeded components.
As a work around, save the original as the new uxml, then edit the new uxml to prevent that from happening.
It would help to use some example names when talking about 2 uxmls, instead of “a uxml” and “another uxml”.
For my own sake, let’s call:
- original UXML: “Original.uxml”
- “another” UXML: “New.uxml”
If I follow you, are you saying that:
- after removing some elements from “Original.uxml”
- and using “Save As” to create a new “New.uxml”,
- when loading back “Original.uxml”,
- it was the same as “New.uxml”?
Sorry, yeah it would be better. I really need to get better at explaining problems.
This is exactly what I did and had happen to me.
Looks like a bug then. Please submit it via Unity’s built-in Bug Reporter for proper tracking.
Filed the bug report with Case 1267416.