Hi all,
I recently implemented a custom force model component and implemented the ModelComponent method "generateDecorations()" to visualize my force within the GUI. However the decorations only show up within the OpenSim visualizer. The GUI seems to ignore them.
Is there an alternative way to equip custom ModelComponents with a graphical representation?
Best regards, Daniel
Decorative Geometry in GUI
- Ayman Habib
- Posts: 2244
- Joined: Fri Apr 01, 2005 12:24 pm
Re: Decorative Geometry in GUI
Hi Daniel,
I'm not sure what version of the code/GUI/API you're using but as of version 3.3 the GUI was not using the generateDecorations route but rather its own custom code that knew only about specific types that can be visualized.
We're moving away from that and current GUI development uses the generateDecorations pathway indeed. Please let me know if you'd like to try that and we can coordinate (since that branch is still in development and is tied to the 4.0 API).
Best regards,
-Ayman
I'm not sure what version of the code/GUI/API you're using but as of version 3.3 the GUI was not using the generateDecorations route but rather its own custom code that knew only about specific types that can be visualized.
We're moving away from that and current GUI development uses the generateDecorations pathway indeed. Please let me know if you'd like to try that and we can coordinate (since that branch is still in development and is tied to the 4.0 API).
Best regards,
-Ayman
- Daniel Krueger
- Posts: 24
- Joined: Fri Jul 09, 2010 12:05 am
Re: Decorative Geometry in GUI
Thanks Ayman,
I think I' ll just wait for the 4.0 release. Since I have some students working with my models It wouldn't make sense to let them work with a pre-release. So we stick with 3.2.
At least I know that my implementation is correct.
Regards,
Daniel
I think I' ll just wait for the 4.0 release. Since I have some students working with my models It wouldn't make sense to let them work with a pre-release. So we stick with 3.2.
At least I know that my implementation is correct.
Regards,
Daniel