Remove keyboard depend#11
Remove keyboard depend#11davetcoleman wants to merge 33 commits intoPickNikRobotics:kinetic-develfrom mcevoyandy:remove_keyboard_depend
Conversation
davetcoleman
left a comment
There was a problem hiding this comment.
Good looking code!
| ${PROJECT_NAME}_imarker_simple | ||
| ${PROJECT_NAME}_gui | ||
| # ${PROJECT_NAME}_manual_tf_alignment | ||
| # ${PROJECT_NAME}_imarker_simple |
There was a problem hiding this comment.
we still want the ability to use the imarker, right?
|
|
||
| # Library | ||
| add_library(${PROJECT_NAME}_imarker_simple | ||
| src/imarker_simple.cpp |
| In `rviz` add the tf panel by: `Panel -> Add New Panel ->TFKeyboardCalGUI` | ||
|
|
||
|
|
||
|
|
There was a problem hiding this comment.
needs to be better integrated into the README
frames.gv
Outdated
| @@ -0,0 +1,8 @@ | |||
| digraph G { | |||
There was a problem hiding this comment.
this and frames.pdf should not be committed
|
|
||
|
|
||
| #ifndef RVIZ_TF_PUBLISHER_H_ | ||
| #define RVIZ_TF_PUBLISHER_H_ |
There was a problem hiding this comment.
TF_KEYBOARD_CAL_RVIZ_TF_PUBLISHER_H_
| <license>BSD</license> | ||
|
|
||
| <url type="website">https://github.com/davetcoleman/tf_keyboard_cal</url> | ||
| <url type="butracker">https://github.com/davetcoleman/tf_keyboard_cal/issues</url> |
There was a problem hiding this comment.
lol... wow, this is misspelled in my package.xml template I have used for all my many ROS Packages
There was a problem hiding this comment.
I noticed a long time ago but it makes me laugh. 'but racker'
Fix eigen warning
Yes, that Keyboard package is what we were using to listen for key strokes. Not sure if there's something in Qt we could use instead.
Started with *.tf, but thought not to since tf is a package and might cause confusion... was going to ask your opinion but forgot about it.
no limit, just my own file type so wanted to make sure that was noted somewhere. I guess the real answer to this and above is to switch to some other supported file type. yaml?
I guess it doesn't need to be in there. Can take that out.
I agree. Open to alternate layouts.
I'll clean up msgs that aren't being used any more or aren't helpful. |
|
@davetcoleman what do you think about the repo name? |
|
But you should use the keyboard.... here some example code for Rviz:
That would be sweet but not super high priority
+1 |
|
@davetcoleman I Just added keyboard functionality when on the manipulation tab. I've got my own opinions about functionality/usability, but want to hear what you think before I make any further changes. No doc, but keyboard layout is the same. Save is not functional at the moment. |
|
@davetcoleman added ability to have an imarker on top of tf... so use keyboard, gui, or just drag the marker around. Need help testing and finding cases where stuff doesn't work. Number of possible edge cases is getting hard to manage. |
|
Think I've got all the functionality in there now... gui, keyboard (same buttons as before), interactive markers & menus if you want them. Could you look over and check out the functionality? I'll work on cleaning up and README when I get back to Boulder. Examples of anything you need to load will be in the Will also work on the format of the GUI since I shouldn't be adding any more buttons. |
| ${PROJECT_NAME}_imarker_simple | ||
| ${PROJECT_NAME}_gui | ||
| # ${PROJECT_NAME}_manual_tf_alignment | ||
| # ${PROJECT_NAME}_imarker_simple |
There was a problem hiding this comment.
I think we need to keep the imarker_simple functionality - I believe I am using it in other projects. Perhaps we can deprecate it if you have replacement functionality, but that would still need to be tick-tocked with the next ROS release
There was a problem hiding this comment.
We can keep the python version but the old c++ version won't work at all since the keyboard package hasn't been updated.
There was a problem hiding this comment.
fyi i've moved the imarker_simple functionality into rviz_visual_tools today, so this functionality is deprecated here
There was a problem hiding this comment.
... i recommend you use it for your imarker needs though
|
|
||
| # Library | ||
| add_library(${PROJECT_NAME}_imarker_simple | ||
| src/imarker_simple.cpp |
CMakeLists.txt
Outdated
| ${catkin_LIBRARIES}) | ||
|
|
||
| # Library | ||
| # add_library(${PROJECT_NAME}_manual_tf_alignment |
There was a problem hiding this comment.
if you kill _manual_tf_alignment, just remove all the commented out code
| @@ -1,3 +1,13 @@ | |||
| # NEW BRANCH | |||
There was a problem hiding this comment.
Better documentation than this please
There was a problem hiding this comment.
Of course :) Was waiting to finish implementing all the functionality I wanted.
frames.gv
Outdated
| @@ -0,0 +1,8 @@ | |||
| digraph G { | |||
There was a problem hiding this comment.
this file should not be committed
|
|
||
| void RvizTFPublisher::publishTFs() | ||
| { | ||
| static tf::TransformBroadcaster br; |
There was a problem hiding this comment.
why are you using a static var here?
There was a problem hiding this comment.
might be left over from an initial attempt to get the functionality I wanted. I'll review and remove if not needed anymore.
There was a problem hiding this comment.
needs to be there, don't understand why though. comes from their example, without it the TFs don't get published.
| namespace tf_keyboard_cal | ||
| { | ||
| struct tf_data{ | ||
| std::size_t id_; |
There was a problem hiding this comment.
again, might be left over from something I tried earlier on. Will review and remove if no longer needed.
There was a problem hiding this comment.
it's used. I keep it there to generate a unique tf even if the user supplies the same names for "to" and "from"
|
@awesomebytes fyi I think we are going to replace your python-based interactive markers tool with this new approach that also includes that functionality |
|
@mcevoyandy I see your point about renaming this package. It hasn't been released since ROS Jade, so for Kinetic and Lunar we could easily rename it. What are you thinking? How about |
|
@mcevoyandy Questions on latest GUI (just built your PR locally again):
|
Wasn't sure how to handle this... not all your markers need menus, but each marker that has a menu will have the same menu. We could load imarkers for all frames... could always just turn the topic off in rviz if you didn't want to see them.
keyboard shortcuts are there, you have to be on the manipulate tab. same keys as before. Save removed and only contained in the save tab. I think the basic functionality is there, just need input on matters like these and help looking for any bugs that show up around edge cases that I haven't thought of. |
|
what about |
|
I like |
|
I'd like to learn more about hosting and maintaining for release... not
sure what it takes. I'll move the code to a `tf_visual_tools` repo tonight
and continue clean up and documentation.
Andy McEvoy | (832) 439 - 6150
…On Wed, Jun 28, 2017 at 10:56 AM, Dave Coleman ***@***.***> wrote:
I like tf_visual_tools! I'm trying to decide if we should rename this
repo or create a new one... I think a new one would be cleanest. Its your
codebase at this point so you should keep it under your name (though I'm
happy to host it and maintain the release process if you want).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABSamf7X9685s5KfVm6r9ntCMLnSLXyxks5sIoXbgaJpZM4No1M7>
.
|
|
Cool - if you don't mind I'd still like to be a maintainer / admin of your repo |
|
what do you mean? replace the imarker stuff in tf_keyboard_cal with
imarker_simple?
Andy McEvoy | (832) 439 - 6150
…On Wed, Jun 28, 2017 at 6:50 PM, Dave Coleman ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In CMakeLists.txt
<#11 (comment)>
:
> LIBRARIES
- ${PROJECT_NAME}_manual_tf_alignment
- ${PROJECT_NAME}_imarker_simple
+ ${PROJECT_NAME}_gui
+# ${PROJECT_NAME}_manual_tf_alignment
+# ${PROJECT_NAME}_imarker_simple
... i recommend you use it for your imarker needs though
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABSamc3Gooc3WiZMxIRpgTnJUKq7ENFaks5sIvTOgaJpZM4No1M7>
.
|
Questions for @mcevoyandy: