[osg-users] Making the composite window disappear

2007-10-19 Thread Sashidhar Guntury
Hi! I'm using the composite viewer, to make a program wherein there are two views of the entire scene. The main view is spread across the screen while the other view lies in a corner. I want the the smaller view to disappear when I click on it (left click.) My handle function is -- bo

Re: [osg-users] Making the composite window disappear

2007-10-19 Thread Sashidhar Guntury
Hi! As a matter of fact, I would want the view to come back by pressing some other key and that can be done using the setNodeMask() function. thanks a lot... Bye! Sashidhar On 10/19/07, Robert Osfield <[EMAIL PROTECTED]> wrote: > > Hi Shadhidar, > > On 10/19/07, Sashidhar Guntury <[EM

Re: [osg-users] Making the composite window disappear

2007-10-19 Thread Robert Osfield
Hi Shadhidar, On 10/19/07, Sashidhar Guntury <[EMAIL PROTECTED]> wrote: > Oops, I forgot to mention that I'm not removing (i.e deleting) > view variable. I actually tried that but since the destructor is protected, > it would not work. To delete just set all the ref_ptr to 0 and it'

Re: [osg-users] Making the composite window disappear

2007-10-19 Thread Sashidhar Guntury
Hi! Oops, I forgot to mention that I'm not removing (i.e deleting) view variable. I actually tried that but since the destructor is protected, it would not work. thanks! Bye On 10/19/07, Sashidhar Guntury <[EMAIL PROTECTED]> wrote: > > Hi! > > I'm using th

Re: [osg-users] Making the composite window disappear

2007-10-19 Thread Sashidhar Guntury
Hi! I'm using the latest version of OSG (2.2) and yeah, the view is defined as a global variable. These are the global variables I have defined. osg::BoundingBox* bb; osgViewer::CompositeViewer viewer; osgViewer::View* topView; osg::ref_ptr gc; osg::ref_ptr traits; to

Re: [osg-users] Making the composite window disappear

2007-10-19 Thread Robert Osfield
Hi Sashidhar, Which version of the OSG are you using? I did some work in the 2.1.x series to help make adding/removing views a bit more robust. You call of viewer.frame() is something that you should drop as the event handler you've written will be called from within frame, so you are in effect