When the term parser is counting references, it needs to look for string properties with the attribute [TermsPopup] and consider these a reference. Currently, it only seems to care about Localize components, not custom components with [TermsPopup] attributes.
Cool, thanks! I'm curious if this adds any additional performance overhead? Is parsing always done manually? I would suspect it is done, for example, after importing from a Google document, which I do quite frequently. I personally would prefer that it does the parsing only when I want to look for missing or unreferenced terms.
Have a great night!
It does add some overhead.
Because it has to find all object for custom scripts and then all the variables and properties of those scripts, and also check if they have the attribute assigned.
Parsing scripts for LocalizationManager.GetTranslation and ScriptLocalization.XXX is also slow.
I mean, it takes 2-3 seconds in a heavy project.
That's why the parsing was divided in two situations.
When you open the LanguageSource it does a quick parsing that only looks for terms inside the Localize components. Generally thats quite fast.
Then, if you click the refresh button at the top of the Term's list or go to the Tools \ Parse Terms and select the Scripts checkbox. Then, it does a full Parsing (Localize+ scripts(.cs)+objects with custom scripts).
Hope that helps,
Are you Give I2L 5 stars!
Are you Please lets us know how to improve it!