CMB issueshttps://gitlab.kitware.com/cmb/cmb/-/issues2018-09-04T17:27:44-04:00https://gitlab.kitware.com/cmb/cmb/-/issues/191Move required ParaView features into CMB2018-09-04T17:27:44-04:00Ben BoeckelMove required ParaView features into CMBThis will allow for a single application to be distributed for all supported use cases. Requires finding out what features need to be exposed in Model Builder.
Cc: @bob.obara @dcthomp @tjcoronaThis will allow for a single application to be distributed for all supported use cases. Requires finding out what features need to be exposed in Model Builder.
Cc: @bob.obara @dcthomp @tjcoronahttps://gitlab.kitware.com/cmb/cmb/-/issues/137Operator result should be passed to view first2017-04-09T16:44:42-04:00David ThompsonOperator result should be passed to view firstCurrently, to execute an operator in the CMB application, one calls `pqSMTKModelPanel::requestOperation()`. As part of this call, `handleOperationResult()` is invoked. However, in order for operator views to provide feedback (e.g., why t...Currently, to execute an operator in the CMB application, one calls `pqSMTKModelPanel::requestOperation()`. As part of this call, `handleOperationResult()` is invoked. However, in order for operator views to provide feedback (e.g., why they aren't able to operate, show a preview of results), the view (especially any custom view widgets) should be given an opportunity to process the results and deny them to other observers.5.0