Hello dev team!
i have recently discovered the amazing link between transits and logixs. Being able to set a sensor from a transit action to trigger a logix has fixed up a few bugs for me and added some new life to the layout.
this did get me thinking about how much more flexibility we could have with this.
If sensor active, sound horn for 100ms on ¡°roster entry¡±.
meaning a button on the layout can easily sound a locomotives horn, regardless of transits etc.
i feel having control of decoder functions via logix could be a powerful tool to simplify a lot of things .
another suggestion with actions is to add an ¡°If roster entry¡± before adding the actions themselves.
this may give better control over specific decoder functions. For instance, having a drop down list of decoder functions based on the selected locomotive.
i haven¡¯t thought this through yet but I figured I¡¯d get the conversation started to see where it leads?
--
Thanks
Mitch
