<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
        {mso-style-priority:99;
        mso-style-link:"Plain Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";
        mso-fareast-language:EN-US;}
span.PlainTextChar
        {mso-style-name:"Plain Text Char";
        mso-style-priority:99;
        mso-style-link:"Plain Text";
        font-family:"Calibri","sans-serif";}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">Utkarsh<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Well functionally speaking it has a couple of differences.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">a) when you create a panel, a button is made, non checkable (stateless effectively) - (code changes to)<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Qt/Components/pqNamedWidgets.cxx<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">b) when the button is clicked, <o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Qt/Core/pqPropertyLinks.cxx<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Qt/Core/pqSMAdaptor.cxx<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Qt/Core/pqSMAdaptor.h<o:p></o:p></p>
<p class="MsoPlainText">Have been tweaked to actually trigger a modified on the proxy, and when the push to the server is made, the vtkObject has a modified triggered. I don’t think the SMProperty on its own would do that. No doubt you would know how to manage
it, but I found that having a CommandProperty allowed me to encapsulate what I wanted without affecting anything else.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">JB<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span lang="EN-US" style="mso-fareast-language:EN-GB">-----Original Message-----<br>
From: Utkarsh Ayachit [mailto:utkarsh.ayachit@kitware.com] <br>
Sent: 09 March 2012 21:18<br>
To: Biddiscombe, John A.<br>
Cc: Zenker, Dr. Matthias; paraview@paraview.org; paraview-developers@paraview.org<br>
Subject: Re: [Paraview-developers] reload data</span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">John,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">(I haven't read the full thread so I may be missing something here, so bear with me)<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I am wondering what's the difference between a vtkSMCommandProperty and vtkSMProperty? ParaView ServerManager does support using vtkSMProperty directly for the purpose you mentioned. Maybe all we need to add is suppose for create the
"push button" when such a property is found in the XML, isn't it?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Utkarsh<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On Fri, Mar 9, 2012 at 9:44 AM, Biddiscombe, John A. <<a href="mailto:biddisco@cscs.ch"><span style="color:windowtext;text-decoration:none">biddisco@cscs.ch</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText">> Matthias,<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Using the topic_CommandProperty branch on the stage git repo<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> I added the following to readers.xml under the<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> <SourceProxy name="XMLUnstructuredGridReaderCore"<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> …<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> <CommandProperty<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> name="Reload"<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> label="Reload Data"<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> command="Modified"<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> si_class="vtkSIProperty"><o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> </CommandProperty><o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> and a button is created inside the panel for the reader (the file
<o:p></o:p></p>
<p class="MsoPlainText">> series reader also needs to expose the property because the reader is
<o:p></o:p></p>
<p class="MsoPlainText">> actually inside the file series reader).<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> When you click the button the client side proxy is marked as modified,
<o:p></o:p></p>
<p class="MsoPlainText">> and when you hit accept the Modified function is called on the server
<o:p></o:p></p>
<p class="MsoPlainText">> side object (the reader) – this then triggers a re-execution and the
<o:p></o:p></p>
<p class="MsoPlainText">> reader rereads from disk.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> All works as expected. I shall see if I can get this accepted into the
<o:p></o:p></p>
<p class="MsoPlainText">> next patch release as I believe it is a very handy capability to have
<o:p></o:p></p>
<p class="MsoPlainText">> in a number of places. I’ll add the xml changes and push them too, but
<o:p></o:p></p>
<p class="MsoPlainText">> perhaps other readers (of the list) might suggest which other readers
<o:p></o:p></p>
<p class="MsoPlainText">> (of files) need this feature added.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> JB<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> From: <a href="mailto:paraview-bounces@paraview.org"><span style="color:windowtext;text-decoration:none">paraview-bounces@paraview.org</span></a>
<o:p></o:p></p>
<p class="MsoPlainText">> <a href="mailto:[mailto:paraview-bounces@paraview.org]">
<span style="color:windowtext;text-decoration:none">[mailto:paraview-bounces@paraview.org]</span></a><o:p></o:p></p>
<p class="MsoPlainText">> On Behalf Of Zenker, Dr. Matthias<o:p></o:p></p>
<p class="MsoPlainText">> Sent: 08 March 2012 10:36<o:p></o:p></p>
<p class="MsoPlainText">> To: <a href="mailto:paraview@paraview.org"><span style="color:windowtext;text-decoration:none">paraview@paraview.org</span></a><o:p></o:p></p>
<p class="MsoPlainText">> Subject: [Paraview] reload data<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Hi,<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> I would like to watch a running transient simulation producing one
<o:p></o:p></p>
<p class="MsoPlainText">> binary vtu file per timestep. Is there a way to reload the current
<o:p></o:p></p>
<p class="MsoPlainText">> data set so that newly written timesteps are included (e.g. in the “Plot selection over time”<o:p></o:p></p>
<p class="MsoPlainText">> filter), without closing and reopening the whole dataset?<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Thank you,<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Matthias<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> _____________________________________________________________________<o:p></o:p></p>
<p class="MsoPlainText">> ERBE Elektromedizin GmbH<o:p></o:p></p>
<p class="MsoPlainText">> Firmensitz: 72072 Tuebingen<o:p></o:p></p>
<p class="MsoPlainText">> Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede<o:p></o:p></p>
<p class="MsoPlainText">> Registergericht: Stuttgart HRB 380137<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">> Paraview-developers mailing list<o:p></o:p></p>
<p class="MsoPlainText">> <a href="mailto:Paraview-developers@paraview.org"><span style="color:windowtext;text-decoration:none">Paraview-developers@paraview.org</span></a><o:p></o:p></p>
<p class="MsoPlainText">> <a href="http://public.kitware.com/mailman/listinfo/paraview-developers">
<span style="color:windowtext;text-decoration:none">http://public.kitware.com/mailman/listinfo/paraview-developers</span></a><o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
</div>
</body>
</html>