Difference between revisions of "Talk:Property Element"
Jump to navigation
Jump to search
imported>JRoush (New page: '''On User# type elements''': I'm not sure why Bethesda didn't have the menu classes set things like magicka cost directly into the String properties of the Text elements that display the...) |
imported>JRoush |
||
| Line 2: | Line 2: | ||
I suspect it's linked to the fact that the src trait of Operator elements doesn't handle relative paths like "me()\some_child_element\some_other_child_element\someproperty." They probably would've had to assign unique indexes to every text element they needed to update, and it was just easier to create these intermediate properties in an element with an existing index. | I suspect it's linked to the fact that the src trait of Operator elements doesn't handle relative paths like "me()\some_child_element\some_other_child_element\someproperty." They probably would've had to assign unique indexes to every text element they needed to update, and it was just easier to create these intermediate properties in an element with an existing index. | ||
[[User:JRoush|JRoush]] 21:17, 22 May 2009 (EDT) | |||
Revision as of 20:17, 22 May 2009
On User# type elements: I'm not sure why Bethesda didn't have the menu classes set things like magicka cost directly into the String properties of the Text elements that display them. I'm reluctant to speculate in the article itself, but if anyone has some insight, let it be heard here.
I suspect it's linked to the fact that the src trait of Operator elements doesn't handle relative paths like "me()\some_child_element\some_other_child_element\someproperty." They probably would've had to assign unique indexes to every text element they needed to update, and it was just easier to create these intermediate properties in an element with an existing index.
JRoush 21:17, 22 May 2009 (EDT)