SMTK issueshttps://gitlab.kitware.com/cmb/smtk/-/issues2020-11-23T18:42:47-05:00https://gitlab.kitware.com/cmb/smtk/-/issues/398Need to provide a mechanism to define Analysis Configurations in a template file2020-11-23T18:42:47-05:00Robert M. O'BaraNeed to provide a mechanism to define Analysis Configurations in a template fileRight now its awkward to define an analysis configuration - instead we need to be abe to define these within the template file itself.Right now its awkward to define an analysis configuration - instead we need to be abe to define these within the template file itself.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/397Exclusive analyses children only work if their label matches their name2020-11-23T18:42:47-05:00Robert M. O'BaraExclusive analyses children only work if their label matches their nameThe issue is that the name is being stored as the enum, not the name to be displayed.The issue is that the name is being stored as the enum, not the name to be displayed.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/396Crash adding resources to manager in threads2021-04-16T17:00:09-04:00David ThompsonCrash adding resources to manager in threadsThe resource manager should be thread-safe as operations may run in threads and need to add resources.
The following patch demonstrates the issue.
```patch
--- a/src/smtk-3.3.0/smtk/resource/testing/cxx/TestResourceManager.cxx
+++ b/sr...The resource manager should be thread-safe as operations may run in threads and need to add resources.
The following patch demonstrates the issue.
```patch
--- a/src/smtk-3.3.0/smtk/resource/testing/cxx/TestResourceManager.cxx
+++ b/src/smtk-3.3.0/smtk/resource/testing/cxx/TestResourceManager.cxx
@@ -8,11 +8,13 @@
// PURPOSE. See the above copyright notice for more information.
//=========================================================================
+ #include <thread>
#include "smtk/common/UUIDGenerator.h"
#include "smtk/resource/Component.h"
#include "smtk/resource/DerivedFrom.h"
#include "smtk/resource/Manager.h"
+ #include "smtk/common/testing/cxx/helpers.h"
namespace
@@ -190,6 +192,22 @@ int TestResourceManager(int /*unused*/, char** const /*unused*/)
resourceManager->resources().get<smtk::resource::IndexTag>().equal_range(indexA);
auto count = std::distance(resourcesByIndex.first, resourcesByIndex.second);
smtkTest(count == 2, "Fetched " << count << " instead of 2 resources by type-index failed.");
-
+ std::vector<std::thread> ts;
+ for(int i = 1; i < 100; ++i){
+ ts.emplace_back(std::thread([&resourceManager, i](){
+ if(i % 2 == 0){
+ auto rsrc = resourceManager->create<ResourceB>();
+ resourceManager->remove(rsrc);
+ }
+ else{
+ auto rsrc = resourceManager->create<ResourceA>();
+ resourceManager->remove(rsrc);
+ }
+
+ }));
+ }
+ for(auto& t : ts){
+ t.join();
+ }
return 0;
}
```https://gitlab.kitware.com/cmb/smtk/-/issues/395Improper include processing2020-11-18T22:38:17-05:00David ThompsonImproper include processingSMTK's string-encoding macros improperly process nested includes; instead of including content from all included files, only the deepest file content is in the output. For instance if `A.xml` includes `B.xml` includes `C.xml`, the output...SMTK's string-encoding macros improperly process nested includes; instead of including content from all included files, only the deepest file content is in the output. For instance if `A.xml` includes `B.xml` includes `C.xml`, the output will only have content from `A.xml` and `C.xml`.
A simple reproducing example is attached:
[naughty-include.tar.gz](/uploads/e1c99f4c0a9efd1a0fcc9c350803b538/naughty-include.tar.gz)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/cmb/smtk/-/issues/394Feature Request: Category "exclude" logic2020-12-01T17:23:11-05:00John TourtellottFeature Request: Category "exclude" logicWith the release of CMB/Truchas with support for coupled heat transfer and fluid flow (Oct 2020), there is a need to specify a Category::Set that includes "Heat Transfer" and explicitly doesn't include "Fluid Flow". (It is needed for the...With the release of CMB/Truchas with support for coupled heat transfer and fluid flow (Oct 2020), there is a need to specify a Category::Set that includes "Heat Transfer" and explicitly doesn't include "Fluid Flow". (It is needed for the Diffusion Solver namelist, which has different properties depending on whether Fluid Flow is included or not.) In terms of the template syntax, the most obvious candidates are
Option 1: add an `<ExcludeCategories>` element
```
<Categories>
<Cat>Heat Transfer</Cat>
</Categories>
<ExcludeCategories>
<Cat>Fluid Flow</Cat>
</ExcludeCategories>
```
Option 2: add an "Exclude" attribute to the `<Cat>` element
```
<Categories>
<Cat>Heat Transfer</Cat>
<Cat Exclude="true">Fluid Flow</Cat>
</Categories>
```
Option 3: add a new element type `<ExcludeCat>`**
```
<Categories>
<Cat>Heat Transfer</Cat>
<ExcludeCat>Fluid Flow</Cat>
</Categories>
```
Option 1 is the preferred choice but this is certainly open for more discussion.
The current use-case only requires one excluded category, but I am presuming we should support a set of excluded categories. In terms of the logic, I think `Categories::Set::passes()` is only true when *all* excluded categories are not passed in (i.e., there is no *any* case for category exclusion).
In terms of implementation, one approach would add a `std::set<std::string>` to store the excluded categories.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/393Extensible ComponentItem crashes qtAttributePreview2021-03-24T11:22:38-04:00John TourtellottExtensible ComponentItem crashes qtAttributePreviewThe qtAttributePreview application crashes when displaying an extensible ComponentItem.
To reproduce:
* Start the qtAttributePreview app with one command-line argument pointing to the attached component-items.sbt file
* Select the "Bod...The qtAttributePreview application crashes when displaying an extensible ComponentItem.
To reproduce:
* Start the qtAttributePreview app with one command-line argument pointing to the attached component-items.sbt file
* Select the "Body-ext" tab and click "New" button => crash
The cause occurs in `qtReferenceItem::createPhraseModel()` which expects a phrase model to be created by the phase model factory. The crash has something to do with the default phrase model configuration (variable `jcfg`) defined at the top of qtReferenceItem.cxx. I didn't look into why this does not crash modelbuilder.
[component-items.sbt](/uploads/7723c3d7adbfb1ad1182627e54f69af3/component-items.sbt)https://gitlab.kitware.com/cmb/smtk/-/issues/390Visibility badge non-functional after resource save/reload2021-04-14T00:39:57-04:00Aron HelserVisibility badge non-functional after resource save/reloadDiscovered with an AEVA resource, but repros in modelbuilder too. Save a resource with once a component invisible, and the visibility badge is locked to invisible on reload:
- From smtk sample data, load data/model/3d/exodus/knee.ex2 wi...Discovered with an AEVA resource, but repros in modelbuilder too. Save a resource with once a component invisible, and the visibility badge is locked to invisible on reload:
- From smtk sample data, load data/model/3d/exodus/knee.ex2 with session::mesh or session::vtk
- Hide one component using the visibility badge in the resource tree
- Save the resource, providing a new filename.
- Close the resource, and load the .smtk file you just saved.
The visibility badge shows the component is invisible, but it's probably showing, and clicking the eyeball does nothing - it doesn't change, and the component visibility doesn't change.
FYI @dcthomp this is present in aevahttps://gitlab.kitware.com/cmb/smtk/-/issues/389qtGroupView Tab Status is Incorrect2020-09-09T13:31:18-04:00Robert M. O'BaraqtGroupView Tab Status is IncorrectThis is a case where an Attribute View has deleted an attribute. The tab contains the attribute view is correct; however, if another tab contained a reference item that was referring to the now deleted attribute, its status is not prope...This is a case where an Attribute View has deleted an attribute. The tab contains the attribute view is correct; however, if another tab contained a reference item that was referring to the now deleted attribute, its status is not properly updated.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/388qtGroupItem's Optional State Changes when calling updateItemData2020-09-09T13:31:41-04:00Robert M. O'BaraqtGroupItem's Optional State Changes when calling updateItemDataIt seems that the enabled state optional Group Item is changed when calling this method.It seems that the enabled state optional Group Item is changed when calling this method.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/387qt5.12.3 and ParaView: warning qglx_findConfig: FBConfig2020-09-08T17:19:38-04:00chart3388qt5.12.3 and ParaView: warning qglx_findConfig: FBConfigUsing the latest ParaView master with QT 5.12.3 I'm getting the following warnings constantly:
```
warning: In unknown, line 0
warning: qglx_findConfig: Failed to finding matching FBConfig (8 8 8 8)
warning: In unknown, line 0
warning: ...Using the latest ParaView master with QT 5.12.3 I'm getting the following warnings constantly:
```
warning: In unknown, line 0
warning: qglx_findConfig: Failed to finding matching FBConfig (8 8 8 8)
warning: In unknown, line 0
warning: qglx_findConfig: Failed to finding matching FBConfig (1 8 8 8)
warning: In unknown, line 0
warning: qglx_findConfig: Failed to finding matching FBConfig (1 1 8 8)
warning: In unknown, line 0
warning: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
```https://gitlab.kitware.com/cmb/smtk/-/issues/384Finish SMTK 3.32020-09-01T10:12:08-04:00Robert M. O'BaraFinish SMTK 3.3<!--
This template is for tracking a release of smtk. Please replace the
following strings with the associated values:
- `VERSION`: e.g. 3.0.0
- `MAJOR`: e.g. 3
- `MINOR`: e.g. 0
Please remove this comment.
-->
# Preparatory ste...<!--
This template is for tracking a release of smtk. Please replace the
following strings with the associated values:
- `VERSION`: e.g. 3.0.0
- `MAJOR`: e.g. 3
- `MINOR`: e.g. 0
Please remove this comment.
-->
# Preparatory steps
- Update smtk guides
- Assemble release notes into `doc/release/notes/smtk-VERSION`.
- [ ] Get positive review and merge.
# Update smtk
If making a release from the `release` branch, e.g., `vMAJOR.MINOR.0-RC2 or above`:
- [x] Update `release` branch for **smtk**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-vVERSION
echo VERSION > version.txt
git commit -m 'Update version number to VERSION' version.txt
git tag -a -m 'SMTK VERSION' vVERSION HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] Get positive review
- [x] `Do: merge`
- Integrate changes to `release` branch
- [x] `git push origin update-to-vVERSION:release vVERSION`
- Update documentation page
- [ ] See `https://github.com/Kitware/paraview-docs/blob/gh-pages/versions.json`
# Upload documentation
- [ ] Verify documentation is uploaded and is correct
# Post-release
- [ ] Write and publish blog post with release notes.
- [ ] Post an announcement in the Announcements category on
[discourse.smtk.org](https://discourse.kitware.com/c/smtk/).
- [ ] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
- [ ] Move unclosed issues to next release milestone in GitLab
/cc @ben.boeckel
/cc @bob.obara
/cc @tjcorona
/cc @dcthompRobert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/383Errors with nightly builds (linux)2021-01-04T10:05:11-05:00John TourtellottErrors with nightly builds (linux)A strange set of errors occur when running modelbuilder from a nightly build downloaded from data.kitware.com. The first symptom is an error message written to the Output Messages when loading an smtk template containing a `<File>` item:...A strange set of errors occur when running modelbuilder from a nightly build downloaded from data.kitware.com. The first symptom is an error message written to the Output Messages when loading an smtk template containing a `<File>` item:
```
Numeric mode unsupported in the posix collation implementation
```
A secondary issue is that numeric keypad input is ignored. I cannot reproduce this with my developer/debug build.
To reproduce:
1. Download nightly build from https://data.kitware.com/#collection/58fa68228d777f16d01e03e5/folder/5980ed698d777f16d01ea0e8
2. Unzip and start modelbuilder
3. Open the attached [example.sbt](/uploads/2e54d821be8ccd44607addf48c08c43b/example.sbt)
4. Look for the error message in the Output Window.
5. Try editing the "number" item with the numeric keypad part of the keyboard.https://gitlab.kitware.com/cmb/smtk/-/issues/382Attribute Read Resource Reorder2020-08-20T16:46:38-04:00chart3388Attribute Read Resource ReorderpqSMTKDisplayAttributeOnLoadBehavior::handleResourceEvent() was triggering the
display of an empty Attribute Resource because our smtk::attribute::Read runs
on a non-main thread. A race condition arises where the single-shot timer
in cas...pqSMTKDisplayAttributeOnLoadBehavior::handleResourceEvent() was triggering the
display of an empty Attribute Resource because our smtk::attribute::Read runs
on a non-main thread. A race condition arises where the single-shot timer
in case EventType::ADDED runs sooner than the from_json() returns, since the
main thread event loop is free, causing an empty Attribute Resoure to be
displayed.
To remedy this, an unmanaged Attribute Resource is created, then added to the
Resource Manager after from_json() completes on the worker thread. This way,
handleResourceEvent() has something to display. Resolving Resource Links has
been removed, because Manager::Add() performs that task.chart3388chart3388https://gitlab.kitware.com/cmb/smtk/-/issues/381Validity not reporting properly for Tiled Group Views2020-07-31T10:31:47-04:00Robert M. O'BaraValidity not reporting properly for Tiled Group ViewsIf you have a Tiled Group View as a child to a Tabbed Group View, its tabbed does not get marked with an alert symbol of the view contains any invalid children.If you have a Tiled Group View as a child to a Tabbed Group View, its tabbed does not get marked with an alert symbol of the view contains any invalid children.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/380Problem with extension::qt::qtAssociation2ColumnWidget with associations whos...2020-07-31T10:16:15-04:00Robert M. O'BaraProblem with extension::qt::qtAssociation2ColumnWidget with associations whose NumberOfRequires > 0Assume you have an association rule that requires at least 1 thing to be associated with the attribute. If you associated n things to the attribute and then disassociate the 1st thing, the widget will indicate that the associations are ...Assume you have an association rule that requires at least 1 thing to be associated with the attribute. If you associated n things to the attribute and then disassociate the 1st thing, the widget will indicate that the associations are invalid.
This is due to the fact that the underlying ReferenceItem's first entry is now unset and therefore invalid.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/379Ability to restrict an attribute name to conform to a regular expression with...2020-07-22T17:29:49-04:00Robert M. O'BaraAbility to restrict an attribute name to conform to a regular expression within an Attribute ViewRobert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/378Reference item crashes in export dialog2020-07-14T16:55:29-04:00John TourtellottReference item crashes in export dialogObserved using smtk:master development build on Ubuntu 16.04
1. Load the `pillbox4.gen` file in smtk/data/model/3d/genesis. Used the
"SMTK importer for Genesis files into smtk::session::vtk::Resource".
2. Using the File ==> Export Si...Observed using smtk:master development build on Ubuntu 16.04
1. Load the `pillbox4.gen` file in smtk/data/model/3d/genesis. Used the
"SMTK importer for Genesis files into smtk::session::vtk::Resource".
2. Using the File ==> Export Simulation menu item, load the attached [export_test.py](/uploads/1d89cfc8b7ca4827f3544b282a9015f0/export_test.py) script.
3. In the export dialog, try to select the "Model" item.
Modelbuilder crashes with this message dumped to the console:
```
terminate called after throwing an instance of 'smtk::common::TypeContainer::BadTypeError'
what(): Type "shared_ptr<Selection>" not available in this container
```
<details>
<summary>Stack trace:</summary>
<p>
<code>
72 0x40f149 /home/john/projects/cmb-master/build/dev-cmb/bin/modelbuilder() [0x40f149]
71 0x7fc10cc8f840 __libc_start_main + 240
70 0x419b40 /home/john/projects/cmb-master/build/dev-cmb/bin/modelbuilder() [0x419b40]
69 0x7fc11617bd30 QCoreApplication::exec() + 128
68 0x7fc1161732ea QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 234
67 0x7fc1161cbe3f QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 95
66 0x7fc1047cc49c g_main_context_iteration + 44
65 0x7fc1047cc3f0 /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a3f0) [0x7fc1047cc3f0]
64 0x7fc1047cc197 g_main_context_dispatch + 679
63 0x7fc0e32c6cba /home/john/projects/qt/qt.io/5.12.4/gcc_64/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x6bcba) [0x7fc0e32c6cba]
62 0x7fc1167cd76b QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 203
61 0x7fc1167f0125 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 261
60 0x7fc1167eeb73 QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 1587
59 0x7fc116174a28 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 264
58 0x7fc11704daa0 QApplication::notify(QObject*, QEvent*) + 688
57 0x7fc1170469ac QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
56 0x7fc1170a0dbb /home/john/projects/qt/qt.io/5.12.4/gcc_64/lib/libQt5Widgets.so.5(+0x1badbb) [0x7fc1170a0dbb]
55 0x7fc11709e620 /home/john/projects/qt/qt.io/5.12.4/gcc_64/lib/libQt5Widgets.so.5(+0x1b8620) [0x7fc11709e620]
54 0x7fc11704cfba QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) + 506
53 0x7fc116174a28 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 264
52 0x7fc11704e07f QApplication::notify(QObject*, QEvent*) + 2191
51 0x7fc1170469ac QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
50 0x7fc1171b68cb QMenu::event(QEvent*) + 139
49 0x7fc117084790 QWidget::event(QEvent*) + 496
48 0x7fc1171b4380 QMenu::mouseReleaseEvent(QMouseEvent*) + 432
47 0x7fc1171b3476 /home/john/projects/qt/qt.io/5.12.4/gcc_64/lib/libQt5Widgets.so.5(+0x2cd476) [0x7fc1171b3476]
46 0x7fc1171ac35a /home/john/projects/qt/qt.io/5.12.4/gcc_64/lib/libQt5Widgets.so.5(+0x2c635a) [0x7fc1171ac35a]
45 0x7fc117042df0 QAction::activate(QAction::ActionEvent) + 272
44 0x7fc1170409d2 QAction::triggered(bool) + 50
43 0x7fc1161a04e9 QMetaObject::activate(QObject*, int, int, void**) + 1625
42 0x7fc118b2a416 /home/john/projects/cmb-master/build/dev-superbuild/install/lib/libpqApplicationComponents-pv5.8.so.1(+0xe0416) [0x7fc118b2a416]
41 0x7fc0cddc0b17 pqExportSimulationReaction::onTriggered() + 17
40 0x7fc0cddf1fdb pqExportSimulationReaction::exportSimulation() + 2495
39 0x7fc117225c67 QDialog::exec() + 407
38 0x7fc1161732ea QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 234
37 0x7fc1161cbe3f QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 95
36 0x7fc1047cc49c g_main_context_iteration + 44
35 0x7fc1047cc3f0 /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a3f0) [0x7fc1047cc3f0]
34 0x7fc1047cc197 g_main_context_dispatch + 679
33 0x7fc0e32c6cba /home/john/projects/qt/qt.io/5.12.4/gcc_64/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x6bcba) [0x7fc0e32c6cba]
32 0x7fc1167cd76b QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 203
31 0x7fc1167f0125 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 261
30 0x7fc1167eeb73 QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 1587
29 0x7fc116174a28 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 264
28 0x7fc11704daa0 QApplication::notify(QObject*, QEvent*) + 688
27 0x7fc1170469ac QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
26 0x7fc1170a0dbb /home/john/projects/qt/qt.io/5.12.4/gcc_64/lib/libQt5Widgets.so.5(+0x1badbb) [0x7fc1170a0dbb]
25 0x7fc11709e620 /home/john/projects/qt/qt.io/5.12.4/gcc_64/lib/libQt5Widgets.so.5(+0x1b8620) [0x7fc11709e620]
24 0x7fc11704cfba QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) + 506
23 0x7fc116174a28 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 264
22 0x7fc11704e07f QApplication::notify(QObject*, QEvent*) + 2191
21 0x7fc117046985 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 117
20 0x7fc1161747bd QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 141
19 0x7fc11713dd80 QComboBoxPrivateContainer::eventFilter(QObject*, QEvent*) + 896
18 0x7fc11727b2a9 QAbstractItemView::setCurrentIndex(QModelIndex const&) + 153
17 0x7fc1161314ad QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) + 157
16 0x7fc1161312da QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) + 42
15 0x7fc1161a04e9 QMetaObject::activate(QObject*, int, int, void**) + 1625
14 0x7fc117146dc5 /home/john/projects/qt/qt.io/5.12.4/gcc_64/lib/libQt5Widgets.so.5(+0x260dc5) [0x7fc117146dc5]
13 0x7fc11713f57b /home/john/projects/qt/qt.io/5.12.4/gcc_64/lib/libQt5Widgets.so.5(+0x25957b) [0x7fc11713f57b]
12 0x7fc11713d6d1 QComboBox::highlighted(int) + 49
11 0x7fc1161a04e9 QMetaObject::activate(QObject*, int, int, void**) + 1625
10 0x7fc0d28b343f /home/john/projects/cmb-master/build/dev-smtk/lib/libsmtkQtExt.so(+0x24843f) [0x7fc0d28b343f]
9 0x7fc0d29982c8 smtk::extension::qtReferenceItemComboBox::highlightItem(int) + 128
8 0x7fc0d293e530 smtk::extension::qtUIManager::selection() const + 28
7 0x7fc0d293fce1 std::shared_ptr<smtk::view::Selection> const& smtk::common::TypeContainer::get<std::shared_ptr<smtk::view::Selection> >() const + 199
6 0x7fc10d802919 /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8d919) [0x7fc10d802919]
5 0x7fc10d802701 /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8d701) [0x7fc10d802701]
4 0x7fc10d8026b6 /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8d6b6) [0x7fc10d8026b6]
3 0x7fc10d80484d __gnu_cxx::__verbose_terminate_handler() + 365
2 0x7fc10cca603a abort + 362
1 0x7fc10cca4438 gsignal + 56
0 0x7fc10cca44c0 /lib/x86_64-linux-gnu/libc.so.6(+0x354c0) [0x7fc10cca44c0]
( 23.622s) [paraview ] :0 FATL| Signal: SIGABRT
</code>
</p>
</details>T.J. CoronaT.J. Coronahttps://gitlab.kitware.com/cmb/smtk/-/issues/376gcc 5.4 cannot compile TypeContainer2020-06-30T11:36:52-04:00John Tourtellottgcc 5.4 cannot compile TypeContainerTried building the latest smtk:master on linux and got a long template error related TypeContainer. I'll paste the full log, but the most salient part seems to be:
```
/home/john/projects/cmb-master/git/smtk/smtk/common/TypeContainer.h:...Tried building the latest smtk:master on linux and got a long template error related TypeContainer. I'll paste the full log, but the most salient part seems to be:
```
/home/john/projects/cmb-master/git/smtk/smtk/common/TypeContainer.h:118:8: required from ‘bool smtk::common::TypeContainer::insert(const Type&) [with Type = std::shared_ptr<smtk::res
ource::Manager>]’
/home/john/projects/cmb-master/git/smtk/smtk/view/PhraseModel.h:241:27: required from here
/usr/include/c++/5/ext/new_allocator.h:120:4: error: no matching function for call to ‘std::pair<const long unsigned int, std::unique_ptr<smtk::common::TypeContainer::Wrapper> >::pair(
std::pair<long unsigned int, smtk::common::TypeContainer::WrapperFor<std::shared_ptr<smtk::resource::Manager> >*>)’
{ ::new((void *)__p) _Up(std::forward<_Args>(__args)...); }
```
[log](/uploads/9b0aabf1fc8331df944df92b21cf59f1/log)T.J. CoronaT.J. Coronahttps://gitlab.kitware.com/cmb/smtk/-/issues/375qtReferenceItem sends out erroneous modified signal2020-07-02T10:33:06-04:00Robert M. O'BaraqtReferenceItem sends out erroneous modified signalWhen qtReferenceItem is created and the underlying attribute item is optional, it calls setOutputModified to properly set the optional checkbox. However that method always calls modified() even if the item was already set to the appropr...When qtReferenceItem is created and the underlying attribute item is optional, it calls setOutputModified to properly set the optional checkbox. However that method always calls modified() even if the item was already set to the appropriate value.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/371Refrain from using siblingAtColumn in order to support Qt versions < 5.112020-06-23T15:14:25-04:00Robert M. O'BaraRefrain from using siblingAtColumn in order to support Qt versions < 5.11This method was recently added and breaks backward compatibility with earlier Qt versions.This method was recently added and breaks backward compatibility with earlier Qt versions.Robert M. O'BaraRobert M. O'Bara