SMTK issueshttps://gitlab.kitware.com/cmb/smtk/-/issues2021-07-07T08:47:29-04:00https://gitlab.kitware.com/cmb/smtk/-/issues/432Errors in tests are not caught2021-07-07T08:47:29-04:00Ben BoeckelErrors in tests are not caughtErrors which occur in tests and are put into the output are not caught or triggering a failed test. There are some tests that purposefully trigger errors. These tests should instead capture the logging output and ensure that the errors t...Errors which occur in tests and are put into the output are not caught or triggering a failed test. There are some tests that purposefully trigger errors. These tests should instead capture the logging output and ensure that the errors that it expects are happening and not put them onto the console. This allows the tests to fail if other, unexpected errors occur.https://gitlab.kitware.com/cmb/smtk/-/issues/430SMTK registrar should use ParaView's auto_start logic2021-06-28T16:08:19-04:00Ben BoeckelSMTK registrar should use ParaView's auto_start logicCurrently, there's a `static std::shared_ptr` which isn't guaranteed to actually run. Instead, it should be placed into a TU that is called in some other way (here, the autostart class).Currently, there's a `static std::shared_ptr` which isn't guaranteed to actually run. Instead, it should be placed into a TU that is called in some other way (here, the autostart class).https://gitlab.kitware.com/cmb/smtk/-/issues/429n^2 behavior observed on VisibilityBadge representationAddedToActiveView/repr...2021-06-26T21:52:06-04:00chart3388n^2 behavior observed on VisibilityBadge representationAddedToActiveView/representationRemovedFromActiveViewWe observed when loading resources and unloading resources the GUI would become unresponsive but would eventually become responsive again. It would progressively become unresponsive for longer with repeated adding and removing resources...We observed when loading resources and unloading resources the GUI would become unresponsive but would eventually become responsive again. It would progressively become unresponsive for longer with repeated adding and removing resources. After doing some debugging started noticing a n^2 behavior occuring. First resource we'd load / unload we'd get 1 connect and disconnect. Second time we'd get 2. Third time 4. Fourth time 8 and so on. We did this with a vanilla modelbuilder and loading OpenFOAM simulation-workflow.
The slow down is coming from / being felt at [VisibilityBadge::representationAddedToActiveView](smtk/extension/paraview/appcomponents/VisibilityBadge.cxx#L468) and [VisibilityBadge::representationRemovedFromActiveView](smtk/extension/paraview/appcomponents/VisibilityBadge.cxx#L481)
FYI: @bob.obara @dcthompDavid ThompsonDavid Thompsonhttps://gitlab.kitware.com/cmb/smtk/-/issues/427Changing selection on a selector view does not refresh the attribute view2021-07-15T17:17:33-04:00chart3388Changing selection on a selector view does not refresh the attribute viewChanging the selection on a selector view does not cause a refresh in the attribute panel. See attached [TestSelector.sbt](/uploads/bff401d3eb2c799022cf86df03ecb804/TestSelector.sbt)
Reproduce with SBT:
1. In tab L change Default dro...Changing the selection on a selector view does not cause a refresh in the attribute panel. See attached [TestSelector.sbt](/uploads/bff401d3eb2c799022cf86df03ecb804/TestSelector.sbt)
Reproduce with SBT:
1. In tab L change Default dropdown to tlt
1. Click new in the Custom tab, this should create nol-0
1. Change Default dropdown to flt. You'll notice nol-0 has disappeared.
1. Click the Test tab
1. Click the L tab. You'll notice nol-0 has reappeared.
Interesting side note it no longer disappears if you change the Default value. It does start to act wonky if you create and delete attributes under Custom. Things start disappearing and reappearing.
Kind of reminds me of #412
FYI: @bob.obara @dcthomphttps://gitlab.kitware.com/cmb/smtk/-/issues/424ReferenceItem appendValue is O(n)2021-06-15T17:06:38-04:00David ThompsonReferenceItem appendValue is O(n)ReferenceItem appendValue is O(n). Note that appendValues (plural) does not have the same performance issue (if all insertions are done with a single call).
1. Do not check if value is already present in storage.
2. Add API to Reference...ReferenceItem appendValue is O(n). Note that appendValues (plural) does not have the same performance issue (if all insertions are done with a single call).
1. Do not check if value is already present in storage.
2. Add API to ReferenceItem, ResourceItem, ComponentItem:
+ contains(x)
+ appendUniqueValue(x)
+ appendUniqueValues(x)
3. Document carefully (and test?) with regard to multiple association.
FYI: @chart3388 @bob.obara @john.tourtellottDavid ThompsonDavid Thompsonhttps://gitlab.kitware.com/cmb/smtk/-/issues/422Investigate const& parameter typo possibilities2021-05-19T07:13:46-04:00Ben BoeckelInvestigate const& parameter typo possibilitiesThe following discussion from !2450 should be addressed:
- [ ] @dcthomp started a [discussion](https://gitlab.kitware.com/cmb/smtk/-/merge_requests/2450#note_957877): (+2 comments)
> Changes to the API like this probably require a...The following discussion from !2450 should be addressed:
- [ ] @dcthomp started a [discussion](https://gitlab.kitware.com/cmb/smtk/-/merge_requests/2450#note_957877): (+2 comments)
> Changes to the API like this probably require a file in `doc/release/notes` noting the change, even if it won't affect many callers.
>
> Also, is there a reason to pass the shared-pointer by value instead of by const reference?
See commit 61d171ec3ba9c6d3236bcbb8a07b3676906dff43 for replacements.https://gitlab.kitware.com/cmb/smtk/-/issues/421ImportResource operation selecting vtk for .sbt files on some platforms.2021-05-25T16:15:12-04:00John TourtellottImportResource operation selecting vtk for .sbt files on some platforms.Our logic for selecting import reader is getting hosed on macos 11 and some Windows systems.
* The vtk session reader accepts *.* so it always is included in the list of choices
* And the list of choices is actually a `std::set<Operatio...Our logic for selecting import reader is getting hosed on macos 11 and some Windows systems.
* The vtk session reader accepts *.* so it always is included in the list of choices
* And the list of choices is actually a `std::set<Operation::Index>` so we cannot control its order.
* So the first one sometimes is the sbt importer and but sometimes the vtk importerhttps://gitlab.kitware.com/cmb/smtk/-/issues/417Extensible group with string item is being squished2022-05-17T17:10:37-04:00chart3388Extensible group with string item is being squishedThe UI does not allow the user to write or see the expression input on the first initial row. Switching back and forth between another tab will show the table correctly. Also if you give the table more width it doesn't squish it either...The UI does not allow the user to write or see the expression input on the first initial row. Switching back and forth between another tab will show the table correctly. Also if you give the table more width it doesn't squish it either. Attached is an SBT to reproduce. [ExtensibleSquished.sbt](/uploads/711a96ba708d19e60fa032b2e9ae29ad/ExtensibleSquished.sbt)
1. Load SBT
1. Click New on HTC Coded Expression
1. Then in box forAll(htc,facei) go to if table and scroll to column htc[facei]= and use the drop down and select constant. This should produces a squished dialog box:
![image](/uploads/3cdf684f60c7898b293a1d41d32e541e/image.png)
Please note that if you make the attribute editor wider the problem goes away:
![image](/uploads/9dcc3bb6a3243a80a385156b23339876/image.png)
One other thing to note is no scroll box comes up which one would expected. if I make the box longer I'm able get the full dialog box.
![image](/uploads/54c7a68f0e4ec4f0cadc8d6683bfb27e/image.png)Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/416"location" of saved resources overrides actual location of resources on save2021-03-31T15:19:50-04:00Ryan Krattigerryan.krattiger@kitware.com"location" of saved resources overrides actual location of resources on save@john.tourtellott@john.tourtellotthttps://gitlab.kitware.com/cmb/smtk/-/issues/411Not enough space given to children. Design discussion2021-03-26T15:29:08-04:00chart3388Not enough space given to children. Design discussionWhen nesting multiple items not enough space is being given to the expanded items below it and is pushing everything to the right of the parent. Attached is an SBT showing the problem. Awaiting design discussion on discourse. [Neste...When nesting multiple items not enough space is being given to the expanded items below it and is pushing everything to the right of the parent. Attached is an SBT showing the problem. Awaiting design discussion on discourse. [NestedStringItems.sbt](/uploads/e327f6c2de91e8f1e452cae0817de155/NestedStringItems.sbt)
![image](/uploads/405954ead752fbbc570fa48e7cde0611/image.png).
FYI: @bob.obara @am300edRobert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/409Cannot create GLX context (Ubuntu 20.04)2021-04-12T09:30:59-04:00John TourtellottCannot create GLX context (Ubuntu 20.04)I cannot run our nightly modelbuilder builds on an old Dell machine running Ubuntu 20.04. On startup, the app crashes with this error message
```
( 0.698s) [paraview ]vtkXOpenGLRenderWindow.:650 ERR| vtkXOpenGLRenderWindow (...I cannot run our nightly modelbuilder builds on an old Dell machine running Ubuntu 20.04. On startup, the app crashes with this error message
```
( 0.698s) [paraview ]vtkXOpenGLRenderWindow.:650 ERR| vtkXOpenGLRenderWindow (0x1831200): Cannot create GLX context. Aborting.
```
I can run paraview builds on this machine, so I am wondering what might be different in our graphics settings compared to paraview.
I'll paste the full stack trace in case that matters.
<details>
<summary>Stack Trace:</summary>
<pre>
34 0x40c4b7 ./bin/modelbuilder() [0x40c4b7]
33 0x7f2e448bb0b3 __libc_start_main + 243
32 0x40bfdd ./bin/modelbuilder() [0x40bfdd]
31 0x416188 ./bin/modelbuilder() [0x416188]
30 0x7f2e4f2b8a61 pqApplicationCore::_paraview_client_environment_complete() + 97
29 0x7f2e47e165aa QMetaObject::activate(QObject*, int, int, void**) + 1850
28 0x40e2a5 ./bin/modelbuilder() [0x40e2a5]
27 0x7f2e4fd37cd9 pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) + 1049
26 0x7f2e4fca1526 pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior(QObject*) + 310
25 0x7f2e4fca13ae pqAlwaysConnectedBehavior::serverCheck() + 174
24 0x7f2e4f310acd pqObjectBuilder::createServer(pqServerResource const&, int) + 605
23 0x7f2e4d47fa6a vtkSMSession::ConnectToSelf(int) + 106
22 0x7f2e4dbb2a78 vtkProcessModule::RegisterSession(vtkSession*) + 376
21 0x7f2e45c3ff92 /home/john/temp/production/nightly/210324/modelbuilder-6.99.0-20210324-Linux-64bit/bin/../lib/libvtkCommon-pv5.9.so.1(+0x792f92) [0x7f2e45c3ff92]
20 0x7f2e45b3abc9 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 25
19 0x7f2e4eac3d50 /home/john/temp/production/nightly/210324/modelbuilder-6.99.0-20210324-Linux-64bit/bin/../lib/libvtkGUISupportQt-pv5.9.so.1(+0x39d50) [0x7f2e4eac3d50]
18 0x7f2e4eab007b /home/john/temp/production/nightly/210324/modelbuilder-6.99.0-20210324-Linux-64bit/bin/../lib/libvtkGUISupportQt-pv5.9.so.1(+0x2607b) [0x7f2e4eab007b]
17 0x7f2e47e165aa QMetaObject::activate(QObject*, int, int, void**) + 1850
16 0x7f2e4f2a6a89 /home/john/temp/production/nightly/210324/modelbuilder-6.99.0-20210324-Linux-64bit/bin/../lib/libpqCore-pv5.9.so.1(+0x7aa89) [0x7f2e4f2a6a89]
15 0x7f2e4f2a37b2 pqServerMjohn@turtleland:~/temp/production/nightly/210324/modelbuilder-6.99.0-20210324-Linux-64bit$
anagerObserver::connectionCreated(long long) + 50
14 0x7f2e47e165aa QMetaObject::activate(QObject*, int, int, void**) + 1850
13 0x7f2e4f35d64c pqServerManagerModel::onConnectionCreated(long long) + 652
12 0x7f2e4f2a2362 pqServerManagerModel::serverAdded(pqServer*) + 50
11 0x7f2e47e165aa QMetaObject::activate(QObject*, int, int, void**) + 1850
10 0x7f2e4fcfd873 pqDefaultViewBehavior::onServerCreation(pqServer*) + 67
9 0x7f2e4d382352 vtkPVSessionCore::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) + 34
8 0x7f2e4d382194 vtkPVSessionCore::GatherInformationInternal(vtkPVInformation*, unsigned int) + 36
7 0x7f2e4d2b6be9 vtkPVRenderingCapabilitiesInformation::CopyFromObject(vtkObject*) + 9
6 0x7f2e4d2b6bac vtkPVRenderingCapabilitiesInformation::GetLocalCapabilities() + 412
5 0x7f2e4c916075 vtkOpenGLRenderWindow::SupportsOpenGL() + 1029
4 0x7f2e4c9b3a32 vtkXOpenGLRenderWindow::WindowInitialize() + 18
3 0x7f2e4c9b764a vtkXOpenGLRenderWindow::CreateAWindow() + 1834
2 0x7f2e448b9859 abort + 299
1 0x7f2e448da18b gsignal + 203
0 0x7f2e460c13c0 /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0) [0x7f2e460c13c0]
( 0.698s) [paraview ] :0 FATL| Signal: SIGABRT
Aborted (core dumped)
</pre>
</details>https://gitlab.kitware.com/cmb/smtk/-/issues/399Python tests crash initializiing iostream (Ubuntu gcc 5.4)2020-12-02T15:40:58-05:00John TourtellottPython tests crash initializiing iostream (Ubuntu gcc 5.4)A strange problem occurs following a completely-clean build of the current cmb-superbuild:master and smtk:master. All python tests crash. Looking in a debbuger shows that the problem occurs in static initialization of iostream, specifica...A strange problem occurs following a completely-clean build of the current cmb-superbuild:master and smtk:master. All python tests crash. Looking in a debbuger shows that the problem occurs in static initialization of iostream, specifically the line
```
static ios_base::Init __ioinit;
```
This gets triggered when the test code uses `smtk.testing.TestCase` class as the base class for a test case. I'll paste the bottom 20 lines of the stack trace below.
```
(gdb) where
#0 0x0000000000194106 in ?? ()
#1 0x00007fffccda9cd7 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/c++/5/iostream:74
#2 0x00007fffccdaa6b3 in _GLOBAL__sub_I_ArrayConvertersReal.cxx(void) () at /home/john/projects/cmb-master/build/dev-superbuild/superbuild/paraview/src/VTK/Accelerators/Vtkm/DataModel/vtkmlib/ArrayConvertersReal.cxx:26
#3 0x00007ffff7de76fa in call_init (l=<optimized out>, argc=argc@entry=6, argv=argv@entry=0x7fffffffdbb8, env=env@entry=0x7fffffffdbf0) at dl-init.c:72
#4 0x00007ffff7de780b in call_init (env=0x7fffffffdbf0, argv=0x7fffffffdbb8, argc=6, l=<optimized out>) at dl-init.c:30
#5 _dl_init (main_map=main_map@entry=0xd0d620, argc=6, argv=0x7fffffffdbb8, env=0x7fffffffdbf0) at dl-init.c:120
#6 0x00007ffff7dec922 in dl_open_worker (a=a@entry=0x7fffffff8c00) at dl-open.c:575
#7 0x00007ffff7de75a4 in _dl_catch_error (objname=objname@entry=0x7fffffff8bf0, errstring=errstring@entry=0x7fffffff8bf8, mallocedp=mallocedp@entry=0x7fffffff8bef, operate=operate@entry=0x7ffff7dec510 <dl_open_worker>, args=args@entry=0x7fffffff8c00) at dl-error.c:187
#8 0x00007ffff7debde9 in _dl_open (file=0x7fffcd2b1940 "/home/john/projects/cmb-master/build/dev-superbuild/install/lib/python3.7/site-packages/vtkmodules/vtkAcceleratorsVTKmDataModel.so", mode=-2147483646, caller_dlopen=0x7ffff7a4b070 <_PyImport_FindSharedFuncptr+432>, nsid=-2, argc=<optimized out>, argv=<optimized out>, env=0x7fffffffdbf0) at dl-open.c:660
#9 0x00007ffff7095f09 in dlopen_doit (a=a@entry=0x7fffffff8e30) at dlopen.c:66
#10 0x00007ffff7de75a4 in _dl_catch_error (objname=0x65e510, errstring=0x65e518, mallocedp=0x65e508, operate=0x7ffff7095eb0 <dlopen_doit>, args=0x7fffffff8e30) at dl-error.c:187
#11 0x00007ffff7096571 in _dlerror_run (operate=operate@entry=0x7ffff7095eb0 <dlopen_doit>, args=args@entry=0x7fffffff8e30) at dlerror.c:163
#12 0x00007ffff7095fa1 in __dlopen (file=file@entry=0x7fffcd2b1940 "/home/john/projects/cmb-master/build/dev-superbuild/install/lib/python3.7/site-packages/vtkmodules/vtkAcceleratorsVTKmDataModel.so", mode=<optimized out>) at dlopen.c:87
#13 0x00007ffff7a4b070 in _PyImport_FindSharedFuncptr (prefix=prefix@entry=0x7ffff7ae28f7 "PyInit", shortname=shortname@entry=0x7fffcd3475d0 "vtkAcceleratorsVTKmDataModel", pathname=pathname@entry=0x7fffcd2b1940 "/home/john/projects/cmb-master/build/dev-superbuild/install/lib/python3.7/site-packages/vtkmodules/vtkAcceleratorsVTKmDataModel.so", fp=fp@entry=0x0) at /home/john/projects/cmb-master/build/dev-superbuild/superbuild/python3/src/Python/dynload_shlib.c:96
#14 0x00007ffff7a18861 in _PyImport_LoadDynamicModuleWithSpec (spec=spec@entry=0x7fffcd2a9710, fp=fp@entry=0x0) at /home/john/projects/cmb-master/build/dev-superbuild/superbuild/python3/src/Python/importdl.c:129
#15 0x00007ffff7a165bd in _imp_create_dynamic_impl (module=<optimized out>, file=<optimized out>, spec=0x7fffcd2a9710) at /home/john/projects/cmb-master/build/dev-superbuild/superbuild/python3/src/Python/import.c:2167
#16 _imp_create_dynamic (module=<optimized out>, args=<optimized out>, nargs=<optimized out>) at /home/john/projects/cmb-master/build/dev-superbuild/superbuild/python3/src/Python/clinic/import.c.h:289
#17 0x00007ffff791a204 in _PyMethodDef_RawFastCallDict (method=0x7ffff7d7f880 <imp_methods+320>, self=0x7ffff7f6bcb0, args=<optimized out>, nargs=1, kwargs=<optimized out>) at /home/john/projects/cmb-master/build/dev-superbuild/superbuild/python3/src/Objects/call.c:530
#18 0x00007ffff791a2c5 in _PyCFunction_FastCallDict (func=0x7ffff7f847d0, args=<optimized out>, nargs=<optimized out>, kwargs=<optimized out>) at /home/john/projects/cmb-master/build/dev-superbuild/superbuild/python3/src/Objects/call.c:586
#19 0x00007ffff78f231a in do_call_core (kwdict=0x7fffcd354b90, callargs=0x7fffcd33d6d0, func=0x7ffff7f847d0) at /home/john/projects/cmb-master/build/dev-superbuild/superbuild/python3/src/Python/ceval.c:4641
#20 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>) at /home/john/projects/cmb-master/build/dev-superbuild/superbuild/python3/src/Python/ceval.c:3191
```https://gitlab.kitware.com/cmb/smtk/-/issues/392Serialize graph resources2020-09-30T10:39:30-04:00David ThompsonSerialize graph resourcesDavid ThompsonDavid Thompsonhttps://gitlab.kitware.com/cmb/smtk/-/issues/391qtGroupItem display problems inside attribute views2020-09-25T09:58:38-04:00John TourtellottqtGroupItem display problems inside attribute viewsThe ATS templates are pretty complicated and we are seeing some layout issues in attribute views when there are more than 1 GroupItem in an attribute. To demonstrate:
* Unzip these template files: [templates.tgz](/uploads/e18990915a51fc...The ATS templates are pretty complicated and we are seeing some layout issues in attribute views when there are more than 1 GroupItem in an attribute. To demonstrate:
* Unzip these template files: [templates.tgz](/uploads/e18990915a51fc9889e9b9857d653e76/templates.tgz).
* Open the `attribute-view-problem.sbt` file in either modelbuilder or qtAttributePreview.
* In the `Process Kernels` tab, create a new attribute and note that the "function" and "WRM evaluators" groups are both fixed height and clipping their content.
Here is a screenshot showing the difference between displaying the same attribute in an Attribute View (left) and Instanced View (right).
![image](/uploads/7a30f3251d511d7799fd9f7fa968f94d/image.png)
Note: This might be a known issue, and is probably related to #377.https://gitlab.kitware.com/cmb/smtk/-/issues/386Setting semi-transparent color affects visibility of other components.2020-09-03T11:22:24-04:00David ThompsonSetting semi-transparent color affects visibility of other components.See aeva/aeva#98 for details and steps to reproduce. This is likely a bug in either the SMTK representation or the composite polydata mapper.
fyi @tjcorona @bob.obaraSee aeva/aeva#98 for details and steps to reproduce. This is likely a bug in either the SMTK representation or the composite polydata mapper.
fyi @tjcorona @bob.obarahttps://gitlab.kitware.com/cmb/smtk/-/issues/385Z-fighting with "Surface with Edges" representation2020-09-02T14:26:08-04:00T.J. CoronaZ-fighting with "Surface with Edges" representationTo reproduce:
- File->New Resource->Regular Grid->3 Dimension
- Select "Surface with Edges"
- Select domainTo reproduce:
- File->New Resource->Regular Grid->3 Dimension
- Select "Surface with Edges"
- Select domainhttps://gitlab.kitware.com/cmb/smtk/-/issues/377qtGroupItem needs scrollbars2020-09-24T17:51:36-04:00Robert M. O'BaraqtGroupItem needs scrollbarsIf a groupItem has lots of elements the UI panel gets overwhelmed.If a groupItem has lots of elements the UI panel gets overwhelmed.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/374Buttons on Window "Create Uniform Grid Information" not selectable while pare...2020-06-23T10:20:11-04:00Bryan CulverButtons on Window "Create Uniform Grid Information" not selectable while parent window is open.# Steps to reproduce:
- Open ModelBuilder and from the menu select "File --> New Resource --> Mesh"
- Select the "Info" button.
## Current results:
New modal or window can be moved around, but all other interactions produce no resul...# Steps to reproduce:
- Open ModelBuilder and from the menu select "File --> New Resource --> Mesh"
- Select the "Info" button.
## Current results:
New modal or window can be moved around, but all other interactions produce no results until the parent window/modal is closed.
## Expected results:
New window displays information about the "Create Uniform Grid" window and should be closed before interaction with the "Create Uniform Grid" window continues.
## Observation notes:
"Information" window cannot be closed and selecting any buttons yields no results until after the "Create Uniform Grid" window is closed. This bug also occurs when using "File --> New Resource --> Polygon"https://gitlab.kitware.com/cmb/smtk/-/issues/373Do not advertise unwanted support for filetypes2020-06-20T10:24:31-04:00David ThompsonDo not advertise unwanted support for filetypesSometimes applications do not want to support filetypes that SMTK supports (e.g., aeva does not want smtk::mesh to advertise its support for STL files, VTK data — see aeva/aeva#43 , aeva/aeva#47 ). SMTK should provide applications with a...Sometimes applications do not want to support filetypes that SMTK supports (e.g., aeva does not want smtk::mesh to advertise its support for STL files, VTK data — see aeva/aeva#43 , aeva/aeva#47 ). SMTK should provide applications with a way to either remove registered reader/importer functionality by filetype or explicitly add filetypes.https://gitlab.kitware.com/cmb/smtk/-/issues/372Resource visibility state is not saved and honored on reload2020-06-17T15:14:59-04:00chart3388Resource visibility state is not saved and honored on reloadIf you open some geometry, toggle the visibility to off in the resource panel, save the resource, and then reload it, the visibility is back on. The state did not follow the save state and reload.If you open some geometry, toggle the visibility to off in the resource panel, save the resource, and then reload it, the visibility is back on. The state did not follow the save state and reload.