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
As the title suggests. This would significantly enable open source sharing and modularization of systems, as it would allow a system to be reused simply by running it and activating the corresponding mode executor. It should therefore come along with the option for mode executors to "finish", and then for other mode executors to reactivate on a finished mode executor. It would allow sharing functionality without the user having to reimplement the internal mode switching logic contained in the mode executor.
What are your thoughts?
The text was updated successfully, but these errors were encountered:
Good input. I considered this when designing the current logic and ended up discarding it because it adds a lot of complexity (the need for hierarchical management, and how a user can interact with it), while something similar is already possible by separating a mode into different tasks.
I won't object though if someone comes up with a nice design and implementation for a hierarchy.
Thank you for great work. This is the future.
As the title suggests. This would significantly enable open source sharing and modularization of systems, as it would allow a system to be reused simply by running it and activating the corresponding mode executor. It should therefore come along with the option for mode executors to "finish", and then for other mode executors to reactivate on a finished mode executor. It would allow sharing functionality without the user having to reimplement the internal mode switching logic contained in the mode executor.
What are your thoughts?
The text was updated successfully, but these errors were encountered: