Philipp Schillinger

Not sure if I can help you that much without further information, but here is some general info: Multiple states in a single file is possible, but will not work...

Thanks for reporting! First, note that there is a configuration field called "Explicit state package" in the FlexBE App Configuration panel to always specify the package as you described. Anyways,...

Should be fixed by the above commit.

Thanks for the pointer @romayiii! Yes, I saw this issue and already had a look at the reason. It is, unfortunately, not as easy to address as the issue here,...

An alternative you can use for waiting: There is an OperatorDecisionState, which does nothing but wait until the operator forces an outcome (if you don't set a suggestion). So you...

I was still not able to reproduce this issue. "Sometimes" sounds like this occurs non-deterministically, do you have any suggestions how to make it more likely to occur? In which...

In some way, yes. From a state-perspective, outcomes can be set to the value of one of the state parameters, see for example the [DecisionState](https://github.com/team-vigir/flexbe_behavior_engine/blob/master/flexbe_states/src/flexbe_states/decision_state.py#L31). However, from a behavior-perspective, the...

Sounds very useful, likely also for others. I agree with your suggestion regarding behaviors, although I would let the behavior merely delegate collecting the properties to the root state machine...

I think it makes a lot of sense and would not expect major problems. However, I personally have not yet worked that much with ROS2 and there is no specific...

Just as a quick update: I used some time during the last days to do a major rework and clean-up of the FlexBE core codebase. As part of this clean-up,...