koobas.hobune.stream
Editor's Inspector Dropdown Lists scroll VERY slowly with no mousewheel
When using a dropdown list in the Inspector for setting editor elements, for example a long list of enums (or in this case, hundreds of localization keys), the list which goes well off the page is incredibly slow to scroll through and you can't use the mousewheel to scroll it any quicker.
Am I missing some way to speed this up? It is massively increasing the time my task is taking, as I need to sit waiting for it to scroll for 30 seconds at a time - multiply that by hundreds of elements and it's going to add an extra day or two.
So far looking around for answers it suggests this is a long-running thing that has never been addressed?
Well, by default most popup and dropdown menus are just ordinary native OS menus. So their behaviour is given by the OS. However if you have some special cases it might be worth it to create your own dropdown menu, maybe with a much larger window and multi column layout. Though for localization keys it might be more appropriate to use some kind of sub grouping. So would be easier to implement this grouping with a GenericMenu in a property drawer. Though you somehow have to decide / provide a way how to group those keys. The GenericMenu just needs a "path like" item name and automatically forms submenus based on that.
Though Instead of using a Generic menu you can always create an actual EditorWindow and show it as popup. However it requires some additional work.
In this case I'm using I2Localization plugin, and I'm hesitant to start hacking it to do what you suggested...
Aaaand now I see you can add sub-menus in the list, e.g. xxx/yyy/zzz. D'oh.
Except then it can't be used by script. Oh well.
Well if you use this I2Localization plugin you might want to reach out to the developer with your concerns. Localization isn't that hard, but of course a comprehensive system gets quite complex very quickly. Since you paid quite a bit of money I would at least drop a feature request if the usability of the system isn't great or is lacking functionality.
In your question you talked about enums. I have never used this plugin but it doesn't looks like they use enums at all since all the localization is data driven. Since they store the keys in their own datastructure it would make sense to allow some sort of grouping. So I would suggest you reach out to the developer of that plugin and ask for advice. I'm sure you're not the only one with that issue. At least any mid to large scale game would have those issues.
Will do. BTW was just using enums as another example (the same would be the case there).
