-
Notifications
You must be signed in to change notification settings - Fork 334
Updated rqt_controller_manager
controller state color scheme to match list_controllers color scheme
#2143
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
Updated rqt_controller_manager
controller state color scheme to match list_controllers color scheme
#2143
Conversation
Not entirely certain why the checks are failing, will have to look into it, these changes shouldn't be causing this imo, let me know if I'm missing something |
the checks are failing because of #2134 |
if theres is a controller that was loaded before, and then you unload it for some reason, I think you should have the option to reload it right? |
I don't think there is a way to reload it manually from this GUI |
how to proceed with this PR? |
I'll check and get back to you |
@soham2560 I just tested it. I understand how it is working now. The parameters inside the controller manager are still present, that's why it is working. This means proper cleanup is not done. As it is functional this way, let's make it nicer. For this case is it possible for you to change from "not loaded" to "unloaded" and use a black icon? |
@saikishor that sounds like a good idea, I have added the changes! (refer 284076c) let me know how it looks |
also, since the |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2143 +/- ##
==========================================
- Coverage 89.30% 89.29% -0.02%
==========================================
Files 139 139
Lines 15502 15502
Branches 1318 1318
==========================================
- Hits 13844 13842 -2
- Misses 1155 1156 +1
- Partials 503 504 +1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Yes, let's remove the red one
Done! refer 4bc3907 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the cleanup. However, I think that the yellow button from inactive state should be called cleanup
and trigger cleanup transition to unconfigured state? Like it is with the hardware components. Or it is the wrong icon and should be cleanup -> unload.
And actually, but not related to this PR? why don't we have the
- unload transition from unconfigured
- deactivate->unload transition from active?
@christophfroehlich sorry for the late reply, I missed that completely, for this PR I think renaming it to "Deactivate, Cleanup and Unload" and changing the icon to match the unloaded state would solve make it technically right, though still not a complete solution (for that refer below comment), let me know if I should move forward with the same |
Good catch, I think we can add that for the controllers, basically every controller should be in one of 4 states (atleast in context of
and you should have 3 options at each state to go to the other ones Let me know how it sounds, I can take care of this in another PR if you want |
Sounds great. We could discuss if it is necessary to have the multi-transition options, or only expose one transition at a time? At least it should be consistent for all, otherwise it gets confusing. |
Let's rename it to cleanup and call only the cleanup transition. Let's fix the rest in the already mentioned future PR. |
sounds good, have added change in 74a0a86, since there is no direct cleanup service (waiting on #1236 I believe), had to do elif action is action_cleanup:
self._deactivate_controller(ctrl.name)
unload_controller(self._node, self._cm_name, ctrl.name)
load_controller(self._node, self._cm_name, ctrl.name) You should now get let me know if its good, I'll open up the other issue till then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Controllers: From unconfigured state we don't have the unload option, but let's fix that in #2151
components: "Deactivate and Cleanup" should be yellow, right?
Yep, missed that, updated in 9ec1db7 |
rqt_controller_manager/rqt_controller_manager/controller_manager.py
Outdated
Show resolved
Hide resolved
…er.py Co-authored-by: Christoph Fröhlich <[email protected]>
one more thing, the led on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM!
you are right. As we don't have a finalized state, let's use the same led (choose which). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks guys. LGTM
Brief
In this PR
rqt_controller_manager
(refer 8098fb7)rqt_controller_manager
controller state color scheme to matchlist_controllers
color scheme #2132How was this tested?
Screenshots: