SMTK issueshttps://gitlab.kitware.com/cmb/smtk/-/issues2018-04-11T01:59:25-04:00https://gitlab.kitware.com/cmb/smtk/-/issues/3Add Modification Tracking to Model2018-04-11T01:59:25-04:00Robert M. O'BaraAdd Modification Tracking to ModelNeed to know when a model needs to be saved.Need to know when a model needs to be saved.Yumin YuanYumin Yuanhttps://gitlab.kitware.com/cmb/smtk/-/issues/150Investigate and resolve discrete session "errors" when loading and SMTK file.2017-07-11T14:23:01-04:00David ThompsonInvestigate and resolve discrete session "errors" when loading and SMTK file.Errors like the following appear when loading discrete sessions:
```
ERROR: Entity 296e338f-a165-4636-9d6a-a5dd6371d060 invalid id 296e338f-a165-4636-9d6a-a5dd6371d060 has no matching CMB model item
INFO: Unknown entity type 0 being tra...Errors like the following appear when loading discrete sessions:
```
ERROR: Entity 296e338f-a165-4636-9d6a-a5dd6371d060 invalid id 296e338f-a165-4636-9d6a-a5dd6371d060 has no matching CMB model item
INFO: Unknown entity type 0 being transcribed.
ERROR: Entity 185e2c04-c9c2-498b-a778-0c766f91d669 invalid id 185e2c04-c9c2-498b-a778-0c766f91d669 has no matching CMB model item
INFO: Unknown entity type 0 being transcribed.
INFO: Model - Read: operation succeeded
INFO: Model - Load File: operation succeeded
```
These should be removed unless they are actually errors (which they do not appear to be since the model is loaded properly).Haocheng LIUHaocheng LIUhttps://gitlab.kitware.com/cmb/smtk/-/issues/210Break sessions out of SMTK core and into plugins2019-09-20T12:20:03-04:00T.J. CoronaBreak sessions out of SMTK core and into pluginsAs more SMTK sessions and extensions are created, it is difficult to track how modifications to SMTK core will affect plugins and extensions that are not part of the SMTK project. One step towards fixing this issue is to extract non-SMTK...As more SMTK sessions and extensions are created, it is difficult to track how modifications to SMTK core will affect plugins and extensions that are not part of the SMTK project. One step towards fixing this issue is to extract non-SMTK core components out of SMTK and into separate repositories. This way, our testing of these components will be on equal footing with the testing of other out-of-core plugins/extensions.