Event Controller suggestions and bug
First the bug:
When attempting to change the threshold of the Event Controller by using the action in a button, It will not work if the threshold is for the angle of a rotor.
Now the Suggestions:
1. It wold be nice to have an interface that opens the Terminal to the specific Event Controller on the Physical controller itself. Like with LCD screens and Programmable blocks and many other blocks that are heavily tied to the Terminal interface.
2. It would be nice to be able to have all of your events and reactions on one physical event controller block. Requiring that each event requires its own event controller is quite cumbersome when considering the physical space any automation of significant complexity would take up. Maybe put a drop down menu in the terminal that can be populated with events by having an "Add Event" button in the Terminal as well. This button would add the settings currently in the event controller to a named item the drop down list and the player could go back and edit those settings by selecting the item in the drop down list which would bring those settings back to the Terminal. All the items in the event drop down list would be active and running. the drop down list could also have check boxes next to each item to enable or disable each one.
I like this feedback
Even if a single large grid event controller can't handle too many events for balance reasons, it should be able to handle four events at least, which also matches the four sets of lights and buttons on its appearance. Without the use of subgrids, multiple large grid event controllers may be required for automation, which is a waste of space.
Even if a single large grid event controller can't handle too many events for balance reasons, it should be able to handle four events at least, which also matches the four sets of lights and buttons on its appearance. Without the use of subgrids, multiple large grid event controllers may be required for automation, which is a waste of space.
I 100% agree with the first suggestion. The front panel should act as a direct interface into the settings of the block. This is especially true of the small grid version, that doesn't even have an access panel at the moment.
I 100% agree with the first suggestion. The front panel should act as a direct interface into the settings of the block. This is especially true of the small grid version, that doesn't even have an access panel at the moment.
Can you make these separate suggestions and bug? I really like the idea of having some sort of terminal sorting for specific blocks at specific terminals.
Can you make these separate suggestions and bug? I really like the idea of having some sort of terminal sorting for specific blocks at specific terminals.
2. Because adding the event-and-action selection must totally happen in a separate block instead of, oh, I don't know, directly the very damn blocks whose state change is supposed to be the trigger in the first place. Yes.
2. Because adding the event-and-action selection must totally happen in a separate block instead of, oh, I don't know, directly the very damn blocks whose state change is supposed to be the trigger in the first place. Yes.
Replies have been locked on this page!