CMB issueshttps://gitlab.kitware.com/cmb/cmb/-/issues2017-12-22T09:28:03-05:00https://gitlab.kitware.com/cmb/cmb/-/issues/185Runtime python plugins2017-12-22T09:28:03-05:00Kim PeveyRuntime python pluginsThe python plugin mechanism is great. After doing some development of plugins, I have some ideas that could make things easier for users/developers.
1. Load failure - Error message for failed imports (this is important because when plu...The python plugin mechanism is great. After doing some development of plugins, I have some ideas that could make things easier for users/developers.
1. Load failure - Error message for failed imports (this is important because when plugins use external packages, the PYTHONPATH and env must be set up properly. this will provide a catch for incorrect setup)
2. Load failure - Error message for failed xml description/ui generation
3. Reloading a currently loaded plugin - Warn, then overwrite existing plugin
4. Add 'recent plugins' list or consider persistence on MB close and reopen.5.0T.J. CoronaT.J. Coronahttps://gitlab.kitware.com/cmb/cmb/-/issues/184Skewed DEMs load with bad data2017-12-01T12:07:24-05:00Kim PeveySkewed DEMs load with bad dataIf you load a DEM with a slight, or not so slight, skew to it, MB will load the DEM into a straight square and fill in the empty tiles with -32767. ALL DEMs that are not perfectly in alignment with the X-Y plane will have this issue. Thi...If you load a DEM with a slight, or not so slight, skew to it, MB will load the DEM into a straight square and fill in the empty tiles with -32767. ALL DEMs that are not perfectly in alignment with the X-Y plane will have this issue. This becomes a visualization issue when the DEM is loaded (since the automatic range is way off) and these false values are also picked up by the interpolator.
![demskew](/uploads/78ccc70a3f4919411d8299a0faa3032f/demskew.PNG)
This happens on 4.2 and 5.05.0Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/182Custom scale in display2017-12-01T10:52:13-05:00Kim PeveyCustom scale in displayWhen you toggle between Solid Color and Point Coordinates, it resets to the original scale and looses the previously set custom scale.
Also, the only way to access the 'set custom scale' is to Edit the color map and go to the 'set ...When you toggle between Solid Color and Point Coordinates, it resets to the original scale and looses the previously set custom scale.
Also, the only way to access the 'set custom scale' is to Edit the color map and go to the 'set custom scale' button from there. It would be better if it was available on the Display panel.
Also, its unclear what the 'use separate color map' button does. Sometimes it switches to a different colormap, sometimes it toggles between two different color maps (both different from my custom map).5.0Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/181Manipulating visualized data2017-11-20T14:48:10-05:00Kim PeveyManipulating visualized dataI have a 150 MB DEM that I've loaded into MB as an auxiliary geometry. Whenever the selection is handled (toggle on or off), the display parameters are changed, or viz is toggled on from previously off, it takes an unexpected amount of t...I have a 150 MB DEM that I've loaded into MB as an auxiliary geometry. Whenever the selection is handled (toggle on or off), the display parameters are changed, or viz is toggled on from previously off, it takes an unexpected amount of time for MB to "think" through the process. With a file of this size, I would expect something as simple as a selection change should occur within, say, a 1 second time frame, not the 15 seconds that I'm seeing.
This isn't a bug, just more of a philosophical discussion on how the viz is handled with larger files (though this is a relatively small file)5.0Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/170Improve Face - Grow operator2017-10-23T11:27:59-04:00Haocheng LIUImprove Face - Grow operatorNow if user selects more than one face as the starting point, the operator would do nothing. A better solution would be using the first face as the starting point and appending the others to the operation result.Now if user selects more than one face as the starting point, the operator would do nothing. A better solution would be using the first face as the starting point and appending the others to the operation result.5.0Haocheng LIUHaocheng LIUhttps://gitlab.kitware.com/cmb/cmb/-/issues/149Review whether the legacy Help panel (pqHelpReaction::showHelp) should be shown.2017-05-19T12:45:02-04:00Alvaro SanchezReview whether the legacy Help panel (pqHelpReaction::showHelp) should be shown.As of CMB 4.1, the legacy dialog was hidden, instead, ModelBuilder exposes CMB and SMTK pdf user guides (generated from the [readthedocs](http://cmb.readthedocs.io/en/master/)).
It is necessary to review whether this panel could be usef...As of CMB 4.1, the legacy dialog was hidden, instead, ModelBuilder exposes CMB and SMTK pdf user guides (generated from the [readthedocs](http://cmb.readthedocs.io/en/master/)).
It is necessary to review whether this panel could be useful to show additional documentation, otherwise some things could be removed from `pqCMBModelBuilderMainWindow`. Likewise, if other applications in CMB would be taking the pdf approach, then their concrete MainWindow classes (and the base class) would need a cleanup.5.0https://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