Script Editors don't show as disabled when closing clusters

[philipbelesky]

Steps:

1. Open a cluster embedded inside a definition
2. Open a GhPython component inside the cluster
3. Save the cluster and return to the main definition
4. The opened editor gives no indication it is disabled/no longer editable

It also might be worth looking into how disabled components could be made obvious. With a few editors open its quite easy to loose track and accidentally work on a disabled component. In my work I just set it so that statusStrip background changes to a strong red, but it might be worth looking at more subtle options - maybe making the text field read-only or similar.

[piac]

I'll chat with David about which events we can attach to, in the case of a closed cluster.

On the read-only editor -- feel free to submit a pull request. I'll leave this open with the purpose of reminding us also of this second, smaller, fix.

Thanks! And thanks for opening the request here.