Trying to use the vtkInformation/vtkInformationKey system for own purposes

[mwestphal (Mathieu Westphal (Kitware))]

Hi @cobo

1. Info down pipeline

To transfer information for a filter to the next filter,use the “KEYS_TO_COPY” information key:

Set size of StringVectorProperty list at loading of state file

Hello, I’ve been working on a ParaView plugin very recently. In the XML definition, I used the following widget: <StringVectorProperty name="ParameterNames" command="SetParameterNames" clean_command="ResetParameterNamesToDefault" information_property="ParameterNameInfo" number_of_elements_per_command="1" repeat_command="1" use_index="1" …

It will not go through the whole pipeline though.

It is possible to have keys copy themselves over and over but you need to create your own key class implementing CopyDefaultInformation (or use a existing one like vtkInformationDataObjectMetaDataKey)

2. Info from server to client

Use Information Properties to send information from the server to the client. You can take a look at Examples/Plugins/PropertyWidgets/Plugin/PropertyWidgetsFilter.xml and it’s information_only property.