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
If you set some pre-defined options for parameter values (such as in this example state), they are accessed incorrectly in the behavior containing the state.
IE, the state itself would be imported as from flexbe_states_package.state_name import StateName in the behavior_name_sm.py file. But then the state's default parameters are accessed as flexbe_states_package.StateName.DefaultParameterName.
I think the fix is to just access the default parameters as StateName.DefaultParameterName.
The text was updated successfully, but these errors were encountered:
It's caused by the value of the default parameter being set in the FlexBE App as package_name.StateName.DefaultParameterName when you click your desired parameter value from the drop-down options. So I guess when you click the drop down the parameter should be set to StateName.DefaultParameterName.
This actually depends on whether the state class name is a duplicate in the workspace or if the respective setting is enabled to consider the state package in addition to the class in general. Still, the completion you pointed out is incorrect in both cases.
If you set some pre-defined options for parameter values (such as in this example state), they are accessed incorrectly in the behavior containing the state.
IE, the state itself would be imported as
from flexbe_states_package.state_name import StateName
in the behavior_name_sm.py file. But then the state's default parameters are accessed asflexbe_states_package.StateName.DefaultParameterName
.I think the fix is to just access the default parameters as
StateName.DefaultParameterName
.The text was updated successfully, but these errors were encountered: