spurious render triggered from auto-generated line edits in display panel
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
[Paraview] auto generated line edits in the display panel Utkarsh Ayachit utkarsh.ayachit at kitware.com Sat Oct 20 10:51:26 EDT 2012
Previous message: [Paraview] auto generated line edits in the display panel
Next message: [Paraview] auto generated line edits in the display panel
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 <burlen.loring at gmail.com> 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