Thanks, Marcus. In the end, my problem turns out to be not having the adequate description in the server manager XML which essentially linked with Cell/Point Data Array selection methods... Here is David's reply. http://www.paraview.org/pipermail/paraview/2011-April/021078.html Best, xunlei -----Original Message----- From: Marcus D. Hanwell [mailto:marcus.hanw...@kitware.com] Sent: Monday, April 18, 2011 2:29 PM To: Xunlei Wu Cc: paraview@paraview.org Subject: Re: [Paraview] VTK_IO_EXPORT vs VTK_EXPORT (VTK_ABI_IMPORT vs VTK_ABI_EXPORT)
On Sat, Apr 16, 2011 at 9:04 PM, Xunlei Wu <xun...@renci.org> wrote: > Thanks a lot, Marcus. > I was hoping to figure out why my plugin dll does not behave the same > way as other internally built reader classes (dlls) which have the > clause of dllexport and dllimport depending on the hosting project. My > plugin dll only specifies dllexport as instructed by ParaView plugin > examples. These internal readers can populate "Cell/Point Array > Status" list in the "Object Inspector" widget -> "Properties" panel, > whereas my reader plugin cannot. Following vtkAVSucdReader.h/cxx does > not work yet. Any hint? Sorry for the divergence of the topic. My real > problem has been posted in > http://www.paraview.org/pipermail/paraview/2011-March/020696.html > I don't think it is a symbol visibility issue, but couldn't really comment beyond that. Plugins are not built against, and so do not require the dllimport logic. Marcus _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
