Readonly Property

[mileswest07]

Currently, the only way to implement a sort of "readonly" property to the tree object is to check for a outside "readonly" flag when techtree.researchNode() is fired. This does not prevent users from clicking on the node and firing the canAfford() and researchNode() functions. Is there a better way? Would a readonly property in the treeConfig object be useful?

Would be used when a developer wants to display his tech tree on a documentation website, but restrict the interactivity that goes with it.

By extension, could a readonly attribute be applied to each individual node, based on external parameters (such as species, etc.), for the purpose of disabling the node from beginning research?

Also, functions toggling the readonly property (or properties) would be useful.

[7yl4r]

I see the utility for a global "readonly", but In what cases would readonly be useful on each node? If you want to stop the node from beginning research it should be disabled or canAfford should return false.

In terms of implementing a readonly tree, perhaps overlaying the canvas with an invisible div to absorb clicks would be better than checking readonly on every click event.