Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backwards Compatibility #547

Merged
merged 2 commits into from Mar 5, 2019
Merged

Conversation

mtschoen-unity
Copy link
Collaborator

Purpose of this PR

Ensure that EditorXR works in older version of Unity, starting with 2017.3

Testing status

Basic smoke test passed in 2017.3.0f3, 2017.4.22f1, 2018.1.0f2, 2018.2.21f1, and 2018.3.7f1.

Technical risk

Low -- Only changes serialized files, and only replaces field names with older versions, which have working upgrade paths

Comments to reviewers

The fist-time setup in 2017.3 is a little broken because of Text Mesh Pro. The "Import TMP Essentials" step fails, but if you can get those files from elsewhere, EditorXR works fine.

I had to revert the Spatial Menu prefab back to its state before #540 because the process for going from 2018.3 to earlier versions is not as straightforward. I removed the missing script reference before converting the prefab, so it shouldn't re-introduce that issue.

Rename prefab fields to work properly in 2018.1 and below;
Find-replace all on:
-  m_SourcePrefab -> m_ParentPrefab
-  m_IsPrefabAsset -> m_IsPrefabParent
-  m_CorrespondingSourceObject -> m_PrefabParentObject
@mtschoen-unity mtschoen-unity merged commit 57918e5 into development Mar 5, 2019
@mtschoen-unity mtschoen-unity deleted the backwards-compatibility branch March 5, 2019 21:45
@mtschoen-unity mtschoen-unity added this to the 0.2.1 milestone Mar 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants