You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add the ability to split an input to an interconnected system #1049
Originally posted by corbinklett October 9, 2024
If I have an input that is external to an interconnected system, and I want this external input to connect into multiple systems contained within, the only way I can think to do this is by using set_input_map. Is there a more elegant way? Even when I use set_input_map, I still get the "unused input" warning.
Part of the motivation for this question is that it is difficult to understand how an external input is being used if you can only specify it in terms of the subsystem that it connects to. It might be intended for the input to connect to multiple subsystems.
It shouldn't be too hard to implement this functionality, and I agree it is natural to create systems in the way you described above (without having to resort to manual construction via set_input_map).
I've looked into this a bit further and implementing the functionality above would require a fairly significant change to the current code. As noted in #1047, this functionality can be implemented using the following syntax:
Activity
murrayrm commentedon Oct 12, 2024
It shouldn't be too hard to implement this functionality, and I agree it is natural to create systems in the way you described above (without having to resort to manual construction via
set_input_map).murrayrm commentedon Nov 23, 2024
I've looked into this a bit further and implementing the functionality above would require a fairly significant change to the current code. As noted in #1047, this functionality can be implemented using the following syntax: