Open osrf-migration opened 6 years ago
Original report (archived issue) by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).
The RenderWindow class works by attaching to an existing GUI window using its ID / window ?at=default&fileviewer=file-view-default#RenderTarget.hh-105 handle string . This currently works for ogre as it already has built-in ?at=default&fileviewer=file-view-default render window support . The ?at=default&fileviewer=file-view-default OptixRenderWindow class is currently just a stub and doesn't do anything.
RenderWindow
For optix, we currently require the user to save the image data a buffer in memory then display it into their own window (e.g. see ?at=default&fileviewer=file-view-default#GlutWindow.cc-95 this line in simple_demo that captures data into image data object example) which requires users to write more code.
It would be nice to have a common RenderWindow API that masks these differences.
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
Original report (archived issue) by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).
The
RenderWindow
class works by attaching to an existing GUI window using its ID / window ?at=default&fileviewer=file-view-default#RenderTarget.hh-105 handle string . This currently works for ogre as it already has built-in ?at=default&fileviewer=file-view-default render window support . The ?at=default&fileviewer=file-view-default OptixRenderWindow class is currently just a stub and doesn't do anything.For optix, we currently require the user to save the image data a buffer in memory then display it into their own window (e.g. see ?at=default&fileviewer=file-view-default#GlutWindow.cc-95 this line in simple_demo that captures data into image data object example) which requires users to write more code.
It would be nice to have a common
RenderWindow
API that masks these differences.