Future Features

• ROS File Templates/Plugin's
  • .launch
  • .msg
  • .srv
  • new package
  • .urdf
  • basic node
  • xcal.yaml
  • user templates
• Launch file tools
  • visualizer
  • auto complete
• Formating tools
  • ROS Format warnings
• User interface to existing ROS tools
  • rosnode List
  • rosparm list
• Dock all existing ROS gui tools
  • rqt
  • SMACH

The wiki isn't entirely clear. Does QT Creator need to be built from source or are the plugin build instructions just based on the source build instructions?

We use catkin tools with install space enabled (catkin config --install).

If we have a CMakeLists.txt that installs the include directory, e.g.

install(DIRECTORY
    include/
  DESTINATION ${CATKIN_GLOBAL_INCLUDE_DESTINATION}
)

This can confuse QtCreator, because now some includes are available in the catkin_ws/src and in the catkin_ws/install folder (after a catkin build). This can be very annoying in practice, because sometimes you ctrl click in QtCreator into a header and make some edits there. After the next catkin build, these edits will be overwritten again with the header from below the src space. All that work will be wasted. This happened a couple of times already to me today.

It would be great if we can get the QtCreator ROS Plugin to tell QtCreator to prefer the includes in src over the ones in install. I'm not sure if this is even technically possible though. @Levi-Armstrong , what do you think? any ideas?

If desired I can provide a minimal example that (stochastically but surely) reproduces this issue.

Does it support melody ros version which runs on binonic?