[Paraview] [Fwd: Migrating custom readers to ParaView3]

[Berk Geveci]

A minor correction to Jean's message. You can (and probably should)
the CVS branch for 3.0. The branch tag is ParaView-3-0. The bug was
fixed on the branch as well. The CVS head is currently going through
some significant changes so I would caution against relying on it for
production work.

-berk

On 6/5/07, Jean Favre <jfavre at cscs.ch> wrote:
> I am replyiing to the mailing list so that everybody can profit.
>
> -------- Original Message --------
> From: Bob Anderson <banderson at mirarco.org>
> To: Jean Favre <jfavre at cscs.ch>
> Date: 04, Jun 2007 09:08 PM
> Subject: Migrating custom readers to ParaView3
>
> I see from the ParaView Digest that you have been successful in
> migrating your custom readers to PV3.
>
> ..........
> I have generated GUI and SM plugins, but a) they don't auto-load using
> PV_PLUGIN_PATH and b) even when loaded through the 'Manage Plugins ...',
> my reader doesn't show up in Open - File types.
>
> I am currently working in Windows XP with VisualStudio.net 2003, but I'd
> sure appreciate your sharing what you learned about the successful
> format for PV3.
>
> ===================================================
>
> Auto-loading was broken and has been fixed in the CVS version thanks to
> Clinton Stimpson.
> You will have to use the CVS head, if you need that functionality now.
>
> Jean
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>


-- 
 Berk Geveci
 Kitware Inc.
 28 Corporate Drive
 Clifton Park, NY, 12065