Might as well hide unused fields in Edit Special Node

[NQNStudios]

For everything that's unused in the current node type, we might as well hide all the UI instead of label it Unused and showing junk values, right?

[NQNStudios]

Do the Unused ones ever change based on the values of other values WITHIN the same node type? That would make it more complicated than I'm thinking.

[CelticMinstrel]

Currently no, but there are a couple nodes where the value of one field affects the meaning of another, so I was thinking of implementing something to update labels based on field values… and there are probably some where the value of a field determines whether another field is used, too.

[NQNStudios]

I can think of a case where I want to add a field that might be used or unused based on another field's value. So this hiding/unhiding should probably be able to be refreshed when any field changes, and could use the string "Unused" as the indicator to hide or show a label and its text box/button.

[CelticMinstrel]

Rather than the string "Unused", I think it makes sense to use the button dictionary (see #607).

[NQNStudios]

Okay. So the button dictionary will be modifiable by the node's fields' focus handlers, then?

[CelticMinstrel]

Sort of something like that, yes, though probably not actually directly modifying it.