Will the Text ever be deprecated and/or seamlessly tie in without replacing all our files with public TMP_Text?
I ask because I made a script that takes all known Text properties and does a 1 to 1 conversion (only for my usage, definitely not stable for public use) that takes a Text component and copies the GO, Adds a new component for the new TMP UGUI Text and then changes all the settings to match and destroys the old GO.
I don’t want all this to be completely undone once a full integration is done and anyone with public TMP_Text are the ones that need to migrate to a public Text etc type of system.
UI.Text will likely remain untouched as well as TMP_Text. The new integrated component is likely to closely mirror the TMP_Text properties but might change.
Having said that, I don’t see why some conversion script / API Updater would not be able to handle the transition / conversion when the new component becomes available.
Thanks for the quick reply Stephan. I think we will go ahead and convert everything to TMP_Text since downscaling to 720p in our prototype is currently unreadable with UGUI Text. The biggest transition is the scripts and linked inspector variables that would break. I may be wrong but I doubt there will be a seamless transition once TMP is fully integrated as that would break too much.