Virtual fence ui #192
Open
Virtual fence ui #192
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will allow users to define the rectangle map. The "center" is currently the corner of the rectangle. Variable names should be changed to reflect this (center to corner) and the center and dimensions calulated when the rectangle has finished being drawn and the ROS message is ready to be published. Also added support for circles but they are not drawable yet.
They now reflect that the region is defined using the corners not the center Also fixed a debug output error. Can't put < and > in the string because that is parsed as an html tag.
While the virtual fence is being drawn the center, width and height of the rectangle is displayed. The units are currently pixels. Next they need to be converted into meters.
Converted fence geometry from pixel space to meters for display as the user is drawing the fence.
Implemented Virtual Fence commands as a custom message type and setup QT signals and slots. The next step is to add a sendVirtualFenceCmd call when the user finishes drawing a fence. Then the pipeline can be debugged.
The center calculation in meters was not properly offset in the conversion from pixel space. Added the VirtualFence msg type - should have been added previously
ROS adapter had comments that were added to the call back handler since the virtual fence branch was created. This commit fixes the merge conflict.
wfvining
suggested changes
Aug 27, 2018
Contributor
wfvining
left a comment
wfvining
left a comment
There was a problem hiding this comment.
What is the intended behavior w.r.t. global/local frame when the box is draw? It seems that if the box is drawn in the local frame then it is in a different position for each robot.
It seems to me that the box should always be treated as if it were drawn in the global frame.
Contributor
|
It also appears that a bug has been introduced causing rqt to crash if the pop-out map is open when the simulation is ended. |
Contributor
|
Just a comment, not a change that I need before merge: Shoud there be a different box displayed for each robot when global frame is not selected? |
Contributor
|
One last change:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an initial version with basic functionality. Holding shift and drawing in the map frame creates a virtual fence.