Re: [Paraview] auto generated line edits in the display panel
Great! hope it's not too bad to fix. I noticed a couple more relating to the auto generation in the display properties. The word wrapping is funky. it wraps even when there is enough space to fit the text on one line. When it wraps the labels overlap each other obscuring the text. The "glyph type" drop down is sized differently from the others. The algorithm that translates xml names into label text doesn't handle acronyms. for example: "NumberOfVTKBlah" in the xml shows up as "Number Of VTKBlah", it would be nicer if it were "Number Of VTK Blah". On 10/20/2012 07:51 AM, Utkarsh Ayachit wrote: I agree this is an issue. I think in the past for display properties we relived on editingFinished(), I believe that could be a reasonable choice still for properties under the display "Section". For the non-display section, we could still use the current signal, or even if we change that to editingFinished(), I wonder if that'd be a major issue. Kyle? Utkarsh On Fri, Oct 19, 2012 at 9:21 PM, burlen wrote: Hi, I'm finding it at times problematic when making changes to line edits in the auto generated display properties panel, that the individual parts of the change triggers a render. For example, if I were to change a parameter from "1" to "0.005" there are 5 renders triggered (0, 0., 0.0, 0.00, 0.005). Of course it's no big deal when working locally with small data but it can be problematic when rendering takes along time. In other cases the intermediate values sent (eg the 4 values 0 to 0.00) are invalid and the render produces either nothing or the incorrect results until the final value is ready. At the same time it seems that in other cases it's a desirable thing for the auto-generated panels to respond immediately to changes for example to make apply button green. So I'm wondering, would it be possible to control this behavior with an xml attribute? for example by connecting to one or the other of the editingFinished or texteEdited signals? Or perhaps for the generation code to select which signal to connect to depending on the context? Since the properties panel is under development I thought it might be a good time to suggest such a change (-: Burlen ___ 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 ___ 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 ___ 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
Re: [Paraview] Scripting Common UI Tasks for Opening Files
If you're using the python trace (under Tools->Start Trace/Stop Trace) you can create a python script that should mimic what you're doing in the GUI. After you stop the trace you have the option of saving it as a macro which will then allow you to click on a widget in the GUI to replay those actions. You could also create a state file (File->Save State) which may also accomplish what you're looking for. If either of those don't work as expected and/or desired, I would recommend emailing back the list with specific problems. Andy On Sun, Oct 21, 2012 at 12:49 PM, Adrien Guillon wrote: > Hi everyone, > > We have simulation results that we frequently visualize in the same way. > We construct a specific pipeline, visualize some parts as wireframe, set a > color scheme, and so on. Unfortunately, this is done manually at the > moment, which means that just opening simulation results can take a few > minutes of clicking around. I'm looking to script this. > > Is there a way to script the UI so that it opens a number of given files, > and adjusts features automatically? My investigations into Python > scripting with Paraview suggest that it cannot directly control the UI, > instead it does analysis using Paraview. > > Any suggestions on how to accomplish some automation? > > AJ > > ___ > 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 > > ___ 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
[Paraview] Scripting Common UI Tasks for Opening Files
Hi everyone, We have simulation results that we frequently visualize in the same way. We construct a specific pipeline, visualize some parts as wireframe, set a color scheme, and so on. Unfortunately, this is done manually at the moment, which means that just opening simulation results can take a few minutes of clicking around. I'm looking to script this. Is there a way to script the UI so that it opens a number of given files, and adjusts features automatically? My investigations into Python scripting with Paraview suggest that it cannot directly control the UI, instead it does analysis using Paraview. Any suggestions on how to accomplish some automation? AJ ___ 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
[Paraview] Paraview Visualization Ambiguity an a 2nd order Tetrahedra
Dear all, I have a mesh which is composed of 2nd order tetrahedral elements, however if this mesh is visualized in paraview then see that inside one 2nd order elements other elements are created. So the displayed number of elements are not correct. I am a rather new user of Paraview. The vtk input file seems to be correct and I am comparing that to Gmsh input files and they match. However, Paraview divides the tetra elements in extra 1st order like elements. I guess I am mistaken at some point. Visualization of data is not a problem since the node data is fine and I am visualizing a vector displacement field on the mesh. The input file is also attached. Any comments are appreciated. Best regards, Umut # vtk DataFile Version 2.0 BLOCK ASCII DATASET UNSTRUCTURED_GRID POINTS 231 double -5.0001e-03 5.0001e-03 0.e+00 -5.0001e-03 -5.0001e-03 0.e+00 -5.0001e-03 2.5001e-03 0.e+00 -5.0001e-03 0.e+00 0.e+00 -5.0001e-03 -2.5001e-03 0.e+00 5.0001e-03 5.0001e-03 0.e+00 2.5001e-03 5.0001e-03 0.e+00 0.e+00 5.0001e-03 0.e+00 -2.5001e-03 5.0001e-03 0.e+00 5.0001e-03 -5.0001e-03 0.e+00 5.0001e-03 -2.5001e-03 0.e+00 5.0001e-03 0.e+00 0.e+00 5.0001e-03 2.5001e-03 0.e+00 -2.5001e-03 -5.0001e-03 0.e+00 0.e+00 -5.0001e-03 0.e+00 2.5001e-03 -5.0001e-03 0.e+00 -3.195138889001e-03 3.195138889001e-03 0.e+00 1.73361001e-03 2.66389001e-04 0.e+00 -2.66389001e-04 -1.73361001e-03 0.e+00 3.2060185185184998e-05 -3.2060185185184998e-05 0.e+00 7.2719907407407000e-04 -3.2271990740741002e-03 0.e+00 3.2271990740741002e-03 -7.2719907407407000e-04 0.e+00 3.2271990740741002e-03 -3.2271990740741002e-03 0.e+00 3.1127314814814998e-04 1.6887268518519000e-03 0.e+00 3.5064120370370002e-03 9.9358796296296001e-04 0.e+00 1.006412037036e-03 3.493587962963e-03 0.e+00 3.5064120370370002e-03 3.493587962963e-03 0.e+00 -1.6887268518519000e-03 -3.1127314814814998e-04 0.e+00 -3.493587962963e-03 -1.006412037036e-03 0.e+00 -9.9358796296296001e-04 -3.5064120370370002e-03 0.e+00 -3.493587962963e-03 -3.5064120370370002e-03 0.e+00 -6.95139000e-04 3.195138889001e-03 0.e+00 -3.195138889001e-03 6.95139000e-04 0.e+00 -1.39027999e-03 1.39027999e-03 0.e+00 -1.9871759259259001e-03 -2.0128240740741000e-03 0.e+00 2.0128240740741000e-03 1.9871759259259001e-03 0.e+00 1.4543981481481001e-03 -1.4543981481481001e-03 0.e+00 -5.0001e-03 -5.0001e-03 1.e-02 5.0001e-03 -5.0001e-03 1.e-02 -2.5001e-03 -5.0001e-03 1.e-02 0.e+00 -5.0001e-03 1.e-02 2.5001e-03 -5.0001e-03 1.e-02 5.0001e-03 5.0001e-03 1.e-02 5.0001e-03 -2.5001e-03 1.e-02 5.0001e-03 0.e+00 1.e-02 5.0001e-03 2.5001e-03 1.e-02 -5.0001e-03 5.0001e-03 1.e-02 2.5001e-03 5.0001e-03 1.e-02 0.e+00 5.0001e-03 1.e-02 -2.5001e-03 5.0001e-03 1.e-02 -5.0001e-03 2.5001e-03 1.e-02 -5.0001e-03 0.e+00 1.e-02 -5.0001e-03 -2.5001e-03 1.e-02 3.20486002e-03 3.20486002e-03 1.e-02 -1.734027778000e-03 2.65972002e-04 1.e-02 2.65972002e-04 -1.734027778000e-03 1.e-02 -2.9997e-04 1.6999e-03 1.e-02 -3.50486001e-03 9.95139002e-04 1.e-02 -1.00486000e-03 3.495138889001e-03 1.e-02 -3.504861
