Next to the mentioned buug, on this sample project, you can see the performance of the localization tables editor. Every action is taking a lot of time. Creating new entry, saving it etc.
Should I create a new report with the same data just for the performance issues?
But that export is now critical to me. Maybe there’s something wrong with the table or its data itself but I really need to export it :).
I am still on 1.0.0-pre.9 because of the “selected locale is null bug”
Ok, the bug is still on pre.10. My idea was correct, it’s caused by the “wrong data”. Two entries are missing english texts - but better error message would be welcomed
These two entries are not having english texts - that’s why the export failed. When I entered a text there and then deleted it, the export is still working. So I suppose they were “null” before (for some reason, maybe just new texts) and after that they are “”.
The next thing what is happening me (and I happened on the reported project as well) is also that when I made a few changes to the tables (new entries, edits, saves), the unity sometimes freezes on one of these actions. Like I need to kill it through task manager. It’s random.
It should happen in my previous performance report. I don’t know how to report that better as unity is hanging up during the described actions in this report.