Signals event no longer directly executable from user interface

Originally it was possible to invoke signals as a third party on behalf of the nodes themselves using buttons on the user-interface. Since v2.1, that kind of behaviour specifically requires Advanced mode: Enable ✓ in the user-interface.

Philosophically it was wrong to allow that behaviour in the first place as it treats Signals/Event as if they were actions. The signal flow was back-to front and could cause confusion in the long run.

A correct approach would be to ensure a corresponding Action is used instead to generate the event i.e. tell the node to emit a signal. This has the added benefit of having that behaviour being scriptable via other nodes, and not just through direct human interaction via the user-interface.

Screen capture of issue: