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
This issue is not a duplicate. Before opening a new issue, please search existing issues.
This issue is not a question, bug report, or anything other than a feature request directly related to this project.
Proposal
LifecycleNode along with rclcpp::Node
Use-Case
This feature helps alot for my robot to have stronger control over node states.
Anything else?
Hi,
I have concern regarding lifecycleNode setup. In the past, the zed has this support. But later removed it. It will be lot helpful. if the lifecycleNode is still available.
The text was updated successfully, but these errors were encountered:
Hi @vijayreddysamula
modifying the Wrapper to use Lifecycle is on our roadmap.
We removed it because of the lack of Lifecycle support in image_transport, but we noticed that image_transport has many other issues. We will re-design this part and transform the ZED Components into Lifecycle components.
Unfortunately, this has not yet been scheduled, hence I cannot provide yet a release date.
Thank you for the update! I'm hoping that the development can move forward sooner. I'm looking forward to seeing the changes and improvements in the future releases.
Preliminary Checks
Proposal
LifecycleNode along with rclcpp::Node
Use-Case
This feature helps alot for my robot to have stronger control over node states.
Anything else?
Hi,
I have concern regarding lifecycleNode setup. In the past, the zed has this support. But later removed it. It will be lot helpful. if the lifecycleNode is still available.
The text was updated successfully, but these errors were encountered: