Different types for GetParent and SetParent?
Best Answer
-
Hi,
This limitation is removed in 6.08 which will be released shortly.
The reason was that the type returned from GetParent might not always be compatible with SetParent (which must have the API type IHasGraphicComponents). In the future the connection will be allowed but will generate an error if the object type is wrong.
Johannes Weiman
Software Engineer
RobotStudio Team, ABB Robotics5
Answers
-
Thanks, good to know. Im taking part in competition organised by ABB in Poland atm, and the deadline for a simulation is in 2 weeks. Any chance that 6.08 ll be released by then?
0 -
Hopefully but not guaranteed. In the meantime, try the attached smart component that converts any object to the proper type for SetParent (if possible).Johannes Weiman
Software Engineer
RobotStudio Team, ABB Robotics1 -
You have no idea how much this SC helped me. Thanks to You I didnt need to use some nasty workarounds. atm my project is much cleaner. Thank you . Could you please compile one more simply SC that would convert object to the proper type for Child in Attacher? I thought about giving a RobotStudio SDK a try myself, but there is not much time left until the deadline of the competition. So maybe after that ;]
0 -
Never mind, I managed to build the smartComponent that I needed. It was easier than i thought ;]
1
Categories
- All Categories
- 5.5K RobotStudio
- 394 UpFeed
- 18 Tutorials
- 13 RobotApps
- 297 PowerPacs
- 405 RobotStudio S4
- 1.8K Developer Tools
- 249 ScreenMaker
- 2.7K Robot Controller
- 309 IRC5
- 59 OmniCore
- 7 RCS (Realistic Controller Simulation)
- 785 RAPID Programming
- AppStudio
- 3 RobotStudio AR Viewer
- 18 Wizard Easy Programming
- 105 Collaborative Robots
- 4 Job listings