<P>Hi,
<P>I posted a message to describe a problem but didn't get any help
<P>In my application, I need to display 2d medical images ( in 3 oientations) using MFC view and inventor (coin3d) API.
<P>in the fourth view, I need to display the 3D model and interact with it.
<P>I create a CMDIChildWnd (like for the 3 windows of coin3d) and add a view to it like in CvtkSdiview. at the display time, it displays the sphere of the vtksdi example but if I move the window, the sphere disappear ( no active rendering) and there is no mouse interaction .
<P>If I create another CMDIChildWnd frame with the same methods and add the same view, it works for both windows. Both windows display the sphere and both windows accept mouse interaction
<P>Can you tell me what's wrong?
<P>thanks in advance
<P> <B><I>"Charl P. Botha" <c.p.botha@its.tudelft.nl></I></B> wrote:
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hi Wahid,<BR><BR>On Thu, 2003-01-30 at 05:15, Wahid Alizada wrote:<BR>> Whenever I issue a renWindow->Render() a new window<BR>> pops up with my visualization, instead of the animation sequence occuring<BR>> in the vtkFlRenderWindowInteractor window. Once the sequence is done, both<BR>> the new window and the vtkFlRenderWindow window are non-interactive.<BR>> <BR><BR>I would recommend writing a few small FLTK examples first. It seems<BR>that you've misunderstood the event-driven programming nature of this<BR>toolkit (and most others). You change the azimuth of your camera 45<BR>times before the FLTK event loop (Fl::run()) has even begun. The<BR>application only really starts when the event loop begins. <BR><BR>You will have to create some GUI control and associate a callback to<BR>it. The callback will be triggered when pressing the button DURING the<BR>fltk event loop. In this callback, you can perform your camera<BR>manipulations.<BR><BR>> <BR>> I don't know why this behavior is occuring.<BR>> ///////////////////////////////////////////////////<BR>> ///////////////////////////////////////////////////<BR>> // my addition<BR>> for( int i = 0; i < 45; i++)<BR>> {<BR>> ren->GetActiveCamera()->Azimuth(i);<BR>> renWindow->Render();<BR>> }<BR>> // end of my addition<BR>> ////////////////////////////////////////////////<BR>> /////////////////////////////////////////////////<BR>> /////////////////////////////////////////////////<BR>> // We can now delete all our references to the VTK pipeline (except for<BR>> // our reference to the vtkFlRenderWindowInteractor) as the objects<BR>> // themselves will stick around until we dereference fl_vtk_window<BR>> ren->Delete();<BR>> renWindow->Delete();<BR>> cone->Delete();<BR>> coneMapper->Delete();<BR>> coneActor->Delete();<BR>> <BR>> // this is the standard way of "starting" a fltk application<BR>> int fl_ret = Fl::run();<BR><BR>-- <BR>charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/<BR>_______________________________________________<BR>This is the private VTK discussion list. <BR>Please keep messages on-topic. Check the FAQ at: <HTTP: vtkfaq cgi-bin public.kitware.com><BR>Follow this link to subscribe/unsubscribe:<BR>http://public.kitware.com/mailman/listinfo/vtkusers</BLOCKQUOTE><p><br><hr size=1>Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !<br>
<a href=http://fr.mail.yahoo.com>Testez le nouveau Yahoo! Mail</a>