Term parser ignores [TermsPopup] attributes

Nice suggestion.

2.8.8a4 now checks all your object with custom scripts. And counts the terms in LocalizedString and those regular strings marked as [TermsPopup].
That happens for both variables and properties.

Also, as always, it detects when you do something like this in your code:

Hope that helps,
Frank

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,
Frank