 |
The custom properties in question contained markup symbols ("" and "<j>") which were confusing GTK. These are now properly escaped. |
 |
Rather than enter a new one, I'll ask in this entry - 1. Should the properties appear as, e.g.: obj_<j>_args_int obj_<j>_args_str ... in the blue folder, or is that a problem? 2. The resulting added property seems to be problematic. When for instance I add the first item in the list, the entity winds up with a key named: obj_<j>_args_int |
|
|
The angle bracket stuff is what is written in the DEF file, it stands for the number you insert (e.g. obj1_2_blah). Previously this was being interpreted as HTML which is used to contrl the text formatting, but because it was not well-formed an error was caused. I have added an extra step to escape the control characters which results in the > stuff. Not sure how best to deal with this, unless I just say that non-alphanumeric characters are not supported and ignored the property altogether, or strip out the characters rather than escaping them. |
 |
Why not change the "editor_bla" strings to something less problematic? |
|
|
I have fixed this by escaping only the display name text, not the property name text (which is used when you click OK in the AddPropertyDialog). It doesn't make much sense to add these properties manually (and you still have to edit in the correct values), but at least it behaves correctly if you do. |
|
|
Okay, I believe I understand the explanations. These values will be ultimately added by the Objectives Editor (WIP) and although it doesn't really make much sense for a user to add them by hand, and they'd have to change "i" and "j" values to the proper number values, they still could do so if they wished, using these (now properly escaped) keys as a template. |
- Anonymous
