If I understand this correctly, the undefined results causes a crash.
With some tests, there still exists some bug for chinese IME not on the D765 support list. like first character unexpect with latin ones in windows 8.1.
So ,I think there still some work to do with the IME though no crucial bug appears. Will do more tests in blendercn.Later.
it is needed for export and import purposises but I can see if I can make changes. I have not worked on this for a while, it was a side project that i had been working on for myself and thought i should share.
@campbellbarton: How can we ensure fcurves on enum properties don't cause undefined results? Should this be handled at fcurves, RNA or BLI_math?
The issue is caused by an fcurve animating the rotation_mode property. This is probably not intentional, but since it's generally allowed it should be handled gracefully. When using the "breakdowner" tool the fcurve at some point sets an invalid enum value outside the allowed -1..6 range for rotation modes:
Confirmed, this is a bit serious, setting to high priority
null de-ref here
Yeah… First of all, next time please add here (mere drag and drop) a simple zip archive, not a windows executable which gives nothing on Linux.