I've tried the new updated version and it works fine on my end. Now it looks very easy to manage the OSG's view within a custom view controller.
I'd like to ask a couple of things, just to understand better how everything works. 1) in GraphicsWindowIOS, beyond the window and view, also a view controller is defined and it is allocated in GraphicsWindowIOS.mm just after the view...is this view controller really needed? How is it used? 2) in the view_test example, at the end of FlipsideViewController,mm file, what is the role of USE_GRAPICSWINDOW_IMPLEMENTATION(IOS) ? I tried by removing it and it looks like that my app still works... Thanks. Alessandro On Thu, May 5, 2011 at 9:24 AM, Alessandro Terenzi <[email protected]>wrote: > Thank you Stefan, I'm going to try it right now... > > Alessandro > > On Wed, May 4, 2011 at 10:22 PM, Stephan Huber <[email protected]>wrote: > >> Hi Alessandro, >> >> I had some time to polish the GraphicsWindowIOS-implementation and it >> should work now to use a GraphicsWindowIOS as part of a bigger >> IOS-application. >> >> on github (https://github.com/stmh/osg/tree/iphone) there's even a new >> example demonstrating the usage. >> >> Basically you create a WindowDataClass with your parent-view as >> parameter, this will instruct GraphicsWindowIOS to add the created view >> to this parent-view, and it does respect the sizes in the traits-object. >> >> After that, you can query the GraphicsWindowIOS-object for the created >> view via dynamic_cast<osgViewer::GraphicsWindowIOS*>(window)->getView(); >> >> See the code inside FlipSideViewController.mm for more details. >> >> These new changes are currently not part of osg-trunk, but I'll submit >> them, as soon as possible. >> >> Please let me know, if this new code works on your end. >> >> cheers, >> >> Stephan >> >> >> >> Am 02.05.11 19:17, schrieb Alessandro Terenzi: >> > Hi, >> > I'm trying to find a way to integrate OSG into a generic app for iOS, >> but >> > I'm facing some problems. Maybe I'm missing something, but as far as >> I've >> > understood, it looks like that, in order to use OSG on iOS, I must >> always >> > use the UIWindow and the corresponding UIView/UIViewController objects >> > created by means of GraphicsWindowIOS::WindowData...but in this way I >> find >> > difficult to later manage those UIView and UIViewController objects >> > especially if I need to integrate them in a dynamic view hierarchy. >> > >> > What I'd like to do is to create a UIView-derived class that >> encapsulates >> > everything required to use OSG to draw in just that view, then I'd like >> to >> > manage that view by my own UIViewController (not related to OSG). >> > >> > Is there a way to do this with what is already available in OSG >> (2.9.13)? If >> > not, can anyone suggest what (beyond creating a context and all OpenGLES >> > related stuff) the UIView-derived class should do from the OSG point of >> > view? >> > >> > Thanks. >> > Alessandro >> > >> > >> > >> > >> > _______________________________________________ >> > osg-users mailing list >> > [email protected] >> > >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> >> _______________________________________________ >> osg-users mailing list >> [email protected] >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> > >
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
