Guild of Writers

I've started work on the GUI for the properties page, and I've hit kind of a snag. Converting numbers to a hex string is slow. Especially in an interpreted language. Doing this everytime someone changes something is not on my list of Ways to Make the Script Faster. I was wondering if perhaps one of the devs could allow the script to accept integers, as well as strings. The Integer path would make export faster, as well, since you don't have to convert it back to an integer afterwards.

Just a thought. Also, dumping any coding onto the main script developers, and not me, is alwys a good thing (just kidding. You guys are way to awesome to do that to)

EDIT: This would also apply to anything else that's really a number, but gets entered as a string... page_num, col_type, footstepsound, and the afforementioned col_flagsN. I think that's all of them.

Sorry for the late reply; I just now noticed this post.

Yes, there are many properties which would make much more sense as integers instead of strings. The code would need to support both, namely because of the existing ages out there that use strings for those properties. We'll add that to the ever-growing to-do list.

Exception: col_flagsN - these are hexidecimal values. Since Blender does not have a "hex" property type, string is the natural choice for these properties.