[vtkusers] Design Patterns in VTK

[rahul kumar]

--- vtkusers-request at vtk.org wrote:
> Send vtkusers mailing list submissions to
> 	vtkusers at vtk.org
> 
> To subscribe or unsubscribe via the World Wide Web,
> visit
> 	http://www.vtk.org/mailman/listinfo/vtkusers
> or, via email, send a message with subject or body
> 'help' to
> 	vtkusers-request at vtk.org
> 
> You can reach the person managing the list at
> 	vtkusers-admin at vtk.org
> 
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of vtkusers digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: Serious(?) flaws in vtk code (Luca
> Picello)
>    2. vtkVolume16Reader (LIAM JAMES ATKINS)
>    3. vtkThreshold by arbitrary array (John Platt)
>    4. Re: Serious(?) flaws in vtk code (Mathieu
> Malaterre)
> 
> --__--__--
> 
> Message: 1
> Date: Wed, 10 Mar 2004 22:02:36 +0100
> From: Luca Picello <luca.picello at libero.it>
> To: John Biddiscombe
> <jbiddiscombe at skippingmouse.co.uk>
> Cc: Xianjin Yang <Yang at AGIUSA.COM>,
> vtkusers at vtk.org,
> 	"William A. Hoffman" <billlist at nycap.rr.com>,
> 	Per Dalgas Jakobsen <pdj at maridan.dk>
> Subject: Re: [vtkusers] Serious(?) flaws in vtk code
> 
> This is a multi-part message in MIME format.
> --------------060402070404040802020201
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
> Content-Transfer-Encoding: 8bit
> 
> Well... I think BCB6 will survive for a long time
> because the new 
> BuilderX is a completely different product and it is
> not mature yet.
> And probably it will be not for a long time: there
> are rumors that 
> Borland will change again the BuilderX platform to
> include wxwindows ( 
> http://www.wxwindows.org ) libraries.
> So stay tuned and help all of us that use BCB all
> day long to fix and 
> upgrade it more because it is powerful but not
> perfect, yet!
> I hope to have time asap to fix the "ProjectDemo"
> myself but I am new to 
> VTK and I do not know how to do it yet.
> Right now the problem disappear even if you compile
> your project and 
> package using runtime dll (Options->Linker->Use
> dynamic RTL).
> Is it a real problem to include borland dlls till
> this problem is solved?
> 
> Luca
> 
> PS: if you believe microsoft .net will be the
> future... well.. it is a 
> completely different product from previous visual
> studio and it is at 
> the same point of builderx.
> Use both of them at your risk :-)
> Take care
> 
> 
> 
> John Biddiscombe wrote:
> 
> >VTK\Examples\GUI\Win32\vtkBorland\ProjectDemo
> >
> >it's the original Borland demo, which has never
> been attended to. Please fix
> >it if you have time. Mind you, now that Borland are
> dumping BCB, it's worth
> >discouraging people from adopting it.
> >
> >JB
> >
> >----- Original Message ----- 
> >From: "William A. Hoffman" <billlist at nycap.rr.com>
> >To: "Xianjin Yang" <Yang at AGIUSA.COM>;
> <vtkusers at vtk.org>
> >Cc: "Per Dalgas Jakobsen" <pdj at maridan.dk>
> >Sent: Wednesday, March 10, 2004 2:13 PM
> >Subject: RE: [vtkusers] Serious(?) flaws in vtk
> code
> >
> >
> >  
> >
> >>Where is Project_vtkDemo?  Can it be fixed so
> other people
> >>do not run into this problem?
> >>
> >>-Bill
> >>
> >>
> >>At 12:32 PM 3/9/2004, Xianjin Yang wrote:
> >>
> >>    
> >>
> >>>Dear all,
> >>>
> >>>I have been using BCB6 + VTK 4.2 and had similar
> problems before.
> >>>To solve Access violation problem related to
> DummyCritSect.Lock() in the
> >>>      
> >>>
> >destructor of vtkPolyData (~vtkPolyData), I did
> these in the
> >Project_vtkDemo:
> >  
> >
> >>>1) Remove everything in the FormDestroy event
> handler.
> >>>2) Add this FormClose event handler. All problems
> should be gone!!
> >>>
> >>>void __fastcall TVTK_Form::FormClose(TObject
> *Sender, TCloseAction
> >>>      
> >>>
> >&Action)
> >  
> >
> >>>{
> >>> if (shrink) shrink->Delete();
> >>> vtkTimerLog::DeallocateTimerLog();
> >>> vtkWindow1->GetRenderer()->RemoveAllProps();
> >>> // VTK_Form->Release();
> >>> // Application->Terminate();
> >>>}
> >>>I am not sure if the last two lines of code are
> required in BCB6.
> >>>
> >>>vtkTimerLog::DeallocateTimerLog() is a fix
> discussed here:
> >>>      
> >>>
>
>><http://public.kitware.com/pipermail/vtkusers/2003-August/019522.html>http:
> >>    
> >>
>
>//public.kitware.com/pipermail/vtkusers/2003-August/019522.html
> >  
> >
> >>>Xianjin Yang, Ph.D.
> >>>
> >>>
> >>>
> >>>-----Original Message----- 
> >>>From: William A. Hoffman
> >>>      
> >>>
>
>[<mailto:billlist at nycap.rr.com>mailto:billlist at nycap.rr.com]
> >  
> >
> >>>Sent: Tuesday, March 09, 2004 10:18 AM
> >>>To: Per Dalgas Jakobsen; vtkusers at vtk.org
> >>>Subject: Re: [vtkusers] Serious(?) flaws in vtk
> code
> >>>
> >>>I have not looked at the BCB Windows code,
> however,
> >>>it seems that you might be able to move the
> creation/destruction
> >>>of the vtk objects to a different spot.   There
> must be some method
> >>>that is called to initialize the BCB objects, and
> another one
> >>>to destroy them.   You could go to some sort of
> lazy create if
> >>>there is no such method.   Basically, the first
> time the vtk object

Hi, 
can anybody listout the design Patterns ( esp. GOF)
used in VTK.
thanks.
rahul
> >>>is used, then create the vtk object.  Then when
> your window gets the
> >>>      
> >>>
> >close event, destroy the vtk object, don't just
> create and destroy the vtk
> >objects in the constructor/destructor of the BCB
> object. All vtk objects
> >should be created after main, and deleted before
> the end of main, and you
> >should have no problem.
> >  
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com