Skip to content

GitLab

Switch branch/tag
  1. 22 Feb, 2021 5 commits
  3. 20 Feb, 2021 5 commits
  5. 19 Feb, 2021 2 commits
  7. 18 Feb, 2021 1 commit
  9. 16 Feb, 2021 2 commits
  11. 15 Feb, 2021 2 commits
  13. 13 Feb, 2021 1 commit
  15. 12 Feb, 2021 3 commits
  17. 10 Feb, 2021 1 commit
  19. 09 Feb, 2021 3 commits
    • Bob Obara's avatar
      Merge topic 'addingActiveCategories' · 9b739548
      Bob Obara authored 
      826a3304 ENH: Added the concept of Active Categories
Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
Acked-by: John Tourtellott's avatarJohn Tourtellott <john.tourtellott@kitware.com>
Merge-request: !2382
      9b739548
    • Bob Obara's avatar
      ENH: Added the concept of Active Categories · 826a3304
      Bob Obara authored 
      The concept of active categories (categories that represent the active concepts of the work flow) have been added to the SMTK attribute system.
They are a set of category strings that are assigned to the Attribute Resource.  The new methods include:

* setActiveCategoriesEnabled - enables/disables active categories (default is false)
* activeCategoriesEnabled - returns the current active categories enable mode
* setActiveCategories - sets the set of active categories
* activeCategories - returns the current set of active categories
* passActiveCategoryCheck - methods to test Categories and Categories::Sets based on the Resource's active categories settings

Both Attribute and Item isValid() methods that use to take in no arguments now take in a bool to indicate if their Resource's active categories state should be used to determine validity.  The parameter is by default set to true.  Note that this does not change previous functionality since the Resource's default is disabled (aka false).

Both Attribute and Item now have an isRelevant method that returns true if they are relevant based on the Resource's active category state.  If the Resource has active categories disabled then these methods will always return true, else the method will test their categories based on the resource's active set.

Added a new aspect called **enforcesCategories**.  In the case where a Reference Item is pointing to Attributes, this property means that the Item is valid iff the Attribute its pointing to is considered relevant (meaning it passes the current set of active categories).

* Added support for Active Categories
* Added support for enforcesCategories - **Note** that this represented by **EnforceCategories**  attribute in XML and as a Key in JSON
* See data/attribute/attribute_collection/refitem-categories.sbt for an example.

```xml
      <ItemDefinitions>
        <Component Name="material" EnforceCategories="true">
          <Accepts>
            <Resource Name="smtk::attribute::Resource" Filter="attribute[type='material']" />
          </Accepts>
        </Component>
      </ItemDefinitions>
```

* All Category related methods have been removed from the UI Manager and now use the active category  mechanism
* qtBaseAttribute Category tests have been changed to take in a shared pointer to an Item instead of a reference to an ItemDefinition. - This was needed since ItemDefinitions do not have a way of getting access to the Resource.

* qtReferenceItemCombobox no longer uses "UseCategories" option in its ItemView.
* Now enforces the new **enforcesCategories** property
* When the item's value becomes invalid due to active category changes, this will now properly update the UI.
      826a3304
    • chart3388's avatar
      Fix false postive unit test for Observers · b8953e86
      chart3388 authored 
      The observer associated with a key returned by
smtk::common::Observers::insert() will be removed from the Observers if
the key is destroyed
      b8953e86
  21. 05 Feb, 2021 2 commits
  23. 02 Feb, 2021 2 commits
  25. 29 Jan, 2021 8 commits
  27. 28 Jan, 2021 2 commits
  29. 27 Jan, 2021 1 commit