[Paraview-developers] Fwd: Custom object panels for writers

Lodron, Gerald Gerald.Lodron at joanneum.at
Fri Mar 14 06:33:27 EDT 2014


Ok, i solved the issue of getting information about the input. I copied it from the calculator widget.

Is there no widget for multiselect arrays of the input? Also the PassArrays filter uses the old panel interface for that purpose. By the way: If i use the PassArray filter in Paraview the output of the filter is an unknown type and PV cannot display that any more... (bug?)

Thanks for support
Gerald

Von meinem Sony Ericsson Live with Walkman gesendet

-------- Originalnachricht --------
Betreff: AW: [Paraview-developers] Custom object panels for writers
Von: "Lodron, Gerald" <Gerald.Lodron at joanneum.at>
An: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Cc:



Hi

Ok, than it seems that my prior work for last 3 weeks is also deprecated.... I now had a look at the "property widgets" and have some questions:

-> In the old "ObjectPanel" I get access to the referenceProxy over referenceProxy() where I could access input information (array names and types etc.) over a cast to pqPipelineFilter. I cannot find such an access from pqPropertyWidget, or am I missing something?

-> Is there a way of passing "information only" information to any output form in paraview. Currently I made a custom object widget and used information only properties with a Getter functionality to give the user feedback about some things of the filter (processing time, number of used iterations, etc.)

I want to really make my toolkit Paraview conform but it is really hard for me to find out the right way....
Thanks,

-----Ursprüngliche Nachricht-----
Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Gesendet: Donnerstag, 13. März 2014 16:24
An: Lodron, Gerald
Cc: Paraview Developer (Paraview-developers at paraview.org)
Betreff: Re: [Paraview-developers] Custom object panels for writers

Gerald,

Custom property panels are deprecated since ParaView 4.0. It's preferrable to use custom "property widgets" instead.

Refer to these wiki pages for details on how to add custom property widgets:

http://paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel
http://paraview.org/Wiki/ParaView/Properties_Panel

Utkarsh


On Thu, Mar 13, 2014 at 3:57 AM, Lodron, Gerald <Gerald.Lodron at joanneum.at> wrote:
> Hello
>
>
>
> I found out that the custom object panel does not work for writers. I
> inherited the pqGPCXWriter from Auto Panel with a throw in the
> constructor (so app should crash if panel is constructed), so I am
> really sure that constructor is never called.
>
>
>
> Here my cmake of the writer plugin:
>
>
>
> set(GUI_INT)
>
> set(GUI_SRCS)
>
> QT4_WRAP_CPP( MOC_SRCS pqGPCXWriter.h)
>
>
>
> ADD_PARAVIEW_OBJECT_PANEL(
>
>         IFACES IFACE_SRCS
>
>         CLASS_NAME pqGPCXWriter
>
>         XML_NAME GPCXWriter
>
>         XML_GROUP writer
>
>         )
>
> list(APPEND GUI_INT
>
>     ${IFACES}
>
>     )
>
> list(APPEND GUI_SRCS
>
>     ${IFACE_SRCS}
>
>     ${MOC_SRCS}
>
>     pqGPCXWriter.cxx
>
>     )
>
> ADD_PARAVIEW_PLUGIN(GPCXPlugin
> "${GPCXPLUGIN_VERSION_MAJOR}.${GPCXPLUGIN_VERSION_MINOR}"
>
>         GUI_INTERFACES ${GUI_INT}
>
>         GUI_SOURCES ${GUI_SRCS}
>
>         SERVER_MANAGER_XML GPCXReader.xml GPCXWriter.xml
>
>         SERVER_MANAGER_SOURCES vtkGPCXReader.cxx vtkGPCXWriter.cxx
>
>         REQUIRED_ON_SERVER )
>
>
>
> With the xml:
>
>
>
> <ServerManagerConfiguration>
>
>
>
>   <ProxyGroup name="writers">
>
>
>
>     <WriterProxy name="GPCXWriter"
>
>                  class="vtkGPCXWriter"
>
>                  label="GPCX Writer">
>
>       <Documentation short_help="Write image data as a TIF file.">
>
>         Writes image data as a GPCX data file. Data must be initially
> constructed from a GPCX reader, currently no support for generated
> data from stratch.
>
>       </Documentation>
>
>
>
>       <InputProperty name="Input" command="SetInputConnection">
>
>         <ProxyGroupDomain name="groups">
>
>           <Group name="sources"/>
>
>           <Group name="filters"/>
>
>         </ProxyGroupDomain>
>
>         <DataTypeDomain name="input_type"
> composite_data_supported="0">
>
>           <DataType value="vtkPolyData"/>
>
>         </DataTypeDomain>
>
>       </InputProperty>
>
>
>
>       <StringVectorProperty name="FileName"
>
>                             command="SetFileName"
>
>                             number_of_elements="1"
>
>                             label="Filename">
>
>         <Documentation>
>
>           The file name of output.
>
>         </Documentation>
>
>       </StringVectorProperty>
>
>
>
>        <StringVectorProperty name="test"
>
>                             command="Settest"
>
>                             number_of_elements="1"
>
>                             >
>
>         <Documentation>
>
>           The file name of output.
>
>         </Documentation>
>
>       </StringVectorProperty>
>
>
>
>       <Hints>
>
>         <Property name="Input" show="0"/>
>
>         <WriterFactory extensions="gpcx"
>
>                        file_description="GPCX data file" />
>
>       </Hints>
>
>
>
>     </WriterProxy>
>
>
>
>   </ProxyGroup>
>
>
>
>
>
> Any suggestions?
>
> _________________________________________________________________
>
>
>
> JOANNEUM RESEARCH Forschungsgesellschaft mbH
>
>
>
> DIGITAL - Institute for Information and Communication Technologies
>
> Steyrergasse 17, 8010 Graz, Austria
>
>
>
> phone: +43 316 876-1751
>
> fax: +43 316 8769-1751
>
> e-mail: gerald.lodron at joanneum.at
>
> web: www.joanneum.at/digital
>
> _________________________________________________________________
>
>
>
> This message and any attached files are confidential and intended
> solely for the addressee(s). Any publication, transmission or other
> use of the information by a person or entity other than the intended
> addressee(s) is prohibited. If you receive this in error please
> contact the sender and delete the material. The sender does not accept
> liability for any errors or omissions as a result of the transmission.
>
>
>
> Please consider the environment before printing this page.
>
>
>
>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>


More information about the Paraview-developers mailing list