Dear Burlen, Thank you for your comments. It does not look like the Xdmf reader has any custom panel methods. It does, however, have some logic which caches file-data characteristics before-after RequestInformation(), which might be wrong-footing state file loading? ( Utilities/Xdmf2/vtk/vtkXdmfReader.h:169 ) This is pure speculation on my part also :)
The effect I am seeing is similar to yours - repeated clicking between pipeline browser filter selections causes Xdmf loader to go from OK to modified state, or state loading brings it in as modified. -Ian > You mention ver 3.14 and loading state files. so to me it sounds likely > to be a different bug. if the xdmf reader makes use of the new > properties panel it may have been fixed. All of this is pure speculation > on my part. Kyle is the authority. > Burlen > On 09/13/2012 10:38 AM, Ian Curington wrote: >> Hello Burlen, Kyle, >> >> I am noticing very similar UI& state file related "marked as >> modified" problems, and wonder if it can be related. Please see >> report at: http://paraview.org/Bug/view.php?id=13317 >> Any suggestions? >> -Ian >> >> Wednesday, August 15, 2012, 5:20:32 PM, you wrote: >> >>> Hi Kyle, >>> Thanks, the following steps reproduce slice filter issue: >>> start paraview, build the following pipeline: >> wavelet source ->> slice >> >>> in the pipeline browser: >>> select wavelet, select slice, select wavelet >>> The slice filter is marked modified. >>> Is there going to be a way of undocking the display properties from the >>> object properties? In our filters/sources with a number of properties >>> having that real estate makes it easier to use. >>> Burlen >>> On 08/15/2012 08:43 AM, Kyle Lutz wrote: >>>> Hi Burlen, >>>> >>>> On Mon, Aug 13, 2012 at 8:50 AM, burlen<[email protected]> wrote: >>>>> I've noticed that the slice filter is having similar issue: apply >>>>> activated >>>>> by selecting in the pipeline browser. In my panels this was because pv is >>>>> creating/destroying the panel as the object is selected/deselected in the >>>>> browser so I had to be more careful during the initialization not to mark >>>>> the object as modified, it's probably a similar issue. >>>> Yes, this behavior has changed with the new panels. Property widgets >>>> should be lightweight and avoid doing any heavy computation or >>>> communication. >>>> >>>> Also, if you could give me a list of steps to reproduce incorrect >>>> modified flag issue I could take a look and fix it for you. >>>> >>>> Cheers, >>>> -kyle >>> _______________________________________________ >>> 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 >> >> -- Best regards, Ian mailto:[email protected] _______________________________________________ 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
