LocalizedString Property in Inspector

Hey there,

First off, thanks much for the asset! Been using it for a little over a week and it's doing exactly what we need so far! I'm running into a small usability issue, though, and I figure I'm maybe doing something wrong? I searched the Localization topics on this forum and haven't seen this question come up:

We have a bunch of UI prefabs that are essentially the same code, just display different data (i.e.: this panel displays Food, that panel displays Water -- same code, just different data values set in the editor). For these prefabs, we set our LocalizedString properties in the Inspector, so that each instance knows what strings to show. Pretty simple:


My problem is: we already have a lot of localized terms, and our list is only going to grow. Using LocalizedString properties in this way, the Inspector just shows a PropertyDrawer with a loooooong list of terms, with no way to type or search for a term.

I'm wondering: am I using LocalizedString objects incorrectly? Is there a better way to do this?

If not, can the Search functionality from the Localize component be added to this PropertyDrawer? Scrolling through the terms is excruciatingly slow!

Thanks much!
-Ben

I had no idea about Categories!

You're right this solution isn't perfect, but it helps a lot. Previously I was using implicit categories by creating strings like AAA_BBB_CCC -- but this is much cleaner and helps on the creation side.

Thanks much!
-Ben