Second level nested proxy property data is not written to .pvsm

Hello!

I’m having a small issue related to saving the data of a proxy property inside another proxy instantiated by another proxy property. The tree looks like this

Main Source Proxy -> Proxy1 -> Proxy2

Main Source Proxy is the filter found in a ParaView pipeline. Proxy2 information does not save into state file. When I save the state file, I get

<Proxy group="filters" type="MainSourceProxyName" id="34523" servers="1">
  <Property name="Input" id="34523.Input" number_of_elements="1">
    <Proxy value="31977" output_port="0"/>
    <Domain name="groups" id="34523.Input.groups"/>
    <Domain name="input_type" id="34523.Input.input_type"/>
  </Property>
  <Property name="Proxy1Name" id="34523.Proxy1Name" number_of_elements="1">
    <Proxy value="34522"/>
    <Domain name="proxy_list" id="34523.Proxy1Name.proxy_list">
      <Proxy value="34522"/>
    </Domain>
  </Property>
</Proxy>

value 34522 points to:

<Proxy group="proxy_group1" type="Proxy1Name" id="34522" servers="1">
  <Property name="Input1" id="34522.Input1">
    <Domain name="groups" id="34522.Input1.groups"/>
    <Domain name="input_type" id="34522.Input1.input_type"/>
  </Property>
  <Property name="Input2" id="34522.Input2">
    <Domain name="groups" id="34522.Input2.groups"/>
    <Domain name="input_type" id="34522.Input2.input_type"/>
  </Property>
  <Property name="Proxy2Name" id="34522.Proxy2Name" number_of_elements="1">
    <Proxy value="34521"/>
    <Domain name="proxy_list" id="34522.Proxy2Name.proxy_list">
      <Proxy value="34521"/>
    </Domain>
  </Property>
</Proxy>

Finding 34521 in the state file gives no results. Proxy1Name is in proxy group “proxy_group1” and Proxy2Name is in proxy group “proxy_group2”.

It would be similar to adding a proxy property to the VoronoiKernel and instantiating a PointVolumeInterpolator in the state file.

I am currently using ParaView 5.7. I don’t think such a case exists in ParaView currently… not that I know of.

I’m able to provide more information if needed.

Thank you,
Patrick Laurin

This issue was fixed just recently: https://gitlab.kitware.com/paraview/paraview/-/issues/19986

Sweet! Thank you!

Patrick Laurin