Philipp Schillinger

It is not the parsing that is slow, it appears to solely be the overhead introduced by starting the subprocesses. If I let Python return immediately, I get about the...

I added the new Python parser as alternative, you can switch it in the settings. It now appears to have roughly the same execution time and warnings are printed whenever...

FYI: > Run 'Check behavior' from external process to aid CI -> See FlexBE/flexbe_app#55: xvfb-run rosrun flexbe_app run_app --offline --check-behaviors catkin run_tests flexbe_app

Switch has finally happened as described above. Instructions on the homepage and the tutorials are updated respectively. In case you still use the Chrome app, please consider switching and let...

Not sure if this is still relevant, but let me still try to answer conceptually. What you describe is indeed not possible and I wouldn't know of a way right...

Thanks for your suggestion, I agree that a feature like this would be helpful. However, I am still struggling with a good idea how to integrate it. A behavior has...

Yes, I would like to add them to the property panel (the one that opens on the right side of the editor) of an included behavior in the same way...

The feature itself has been added to a new branch and works already: *feature/sub_parameters* However, supporting it from the user interface side requires changes to code generation/parsing as well as...

@Errogant the feature is now available, can you test if it addresses sufficiently what you had in mind? To test it, please switch to the branch "feature/sub_parameters" in both the...

Building or cleaning should not make any difference here, nothing of the changes depends on a re-build. If you are on the correct branches, a change you should see is...