Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use one behavior's userdata in another behavior without re-creating them #28

Open
FanhuiJ opened this issue Dec 10, 2018 · 1 comment
Open

Comments

@FanhuiJ
Copy link

FanhuiJ commented Dec 10, 2018

Hi, I want to use the same userdata for two different behaviors, does it possible to save a behavior's state machine userdata, then load them into another behavior?

I tried to copy the content of the first behavior's create function (for example: _state_machine.userdata.global_planner = "GlobalPlanner"), then past the content into the [MANUAL_CREATE] section of the second behavior's create function. With this operation, while opening the second behavior, I get these userdata in the State Machine Interface section (such as : Input Keys: global_planner), but nothing in the State Machine Userdata section.

I would like to know if it is possible to copy the userdata value as well, to avoid re-create again those userdata.

Thanks in advance.

@FanhuiJ FanhuiJ closed this as completed Dec 11, 2018
@FanhuiJ FanhuiJ reopened this Dec 11, 2018
@FanhuiJ FanhuiJ closed this as completed Dec 11, 2018
@FanhuiJ FanhuiJ reopened this Dec 12, 2018
@FanhuiJ
Copy link
Author

FanhuiJ commented Dec 12, 2018

I want to edit the issue content, I just couldn't.. For using one behavior's userdata into another behavior, a way is to change the behavior's name, so that another behavior will be created, which is the same as this one but with different name.

When using a container, we need to re-write input and output keys that will be used inside the container, and which are already declared in the Behavior Dashboard. When it concerns many input and output keys, it takes time to re-write them.

Also, sometimes, some output keys of a container should be declared as its input keys as well. Otherwise, warning messages will appear when saving the behavior.

Does it possible to use directly userdata that declared in the Behavior Dashboard inside a container, without re-write them?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant