GitLab

CMP0115 requires test names passed to `smtk_add_test` to
include the filetype extension.

The `smtk_add_test` macro was not properly escaping labels
so if developers specified multiple labels they were not
passed to `set_tests_properties(LABELS ...)` properly.

A lot of test labels in SMTK were not consistently named
(bad capitalization and other variations).

Hopefully this will fix intermittent test failures due to
platform-specific viewport sizing/zoom issues.

Also, properly avoid updating the item during interaction (drag)
events and properly signal modification to parent view.

* Added std::string ValueItem::valueLabel(ith) - convenience method to accede its definition’s valueLabel method

* Changed to qtBaseAttributeView
    * CategoryTest was changed to take in a const attribute::ItemDefinitionPtr& instead of an attribute::ItemPtr since only the definition is needed.  This also eliminated the construction/destruction of a shared pointer.
    * Added displayItemDefinition method which is similar to displayItem.
    * isItemWriteable now takes in a const attribute::ItemPtr & instead of a attribute::ItemPtr which eliminates  the construction/destruction of a shared pointer.
   * advaceLevelTest now takes in a const attribute::ItemPtr & instead of a attribute::ItemPtr which eliminates  the construction/destruction of a shared pointer.

* qtAttributeInternal now stores a QPointer  to a qtBaseAttributeView instead of a qtBaseView - this is more conceptually consistent and eliminated the need for dynamic casts.

* Changes to qtAttributeItemInfo
    * Now stores a QPointer  to a qtBaseAttributeView instead of a qtBaseView - this is more conceptually consistent and eliminated the need for dynamic casts.
    * Changed the API not to require it to be passed as a QPointer which was also unnecessary.

* Changes to qtUIManager
    * Added the following methods that take into consideration the current text color (which changes based on the system’s theme):
         * correctedInvalidColor()
         * correctedDefaultColor()
         * correctedNormalColor()

A method has been removed from ParaView's point-picking helper
class for property widgets (the functionality is now automatic).
Detect this and avoid referencing the method.

Without these, tests cannot modify many items in the operation-view panel.

Originally, widgets would update attributes which would trigger an update
for the widgets, and so on. This update breaks that loop by "capturing" the
update from attribute to widget that occurs as a result of an update from
widget to attribute.

Several updates to ViewWidget registration:
1. Fully decouple smtk::view from smtk::extension
2. Reference registered views by type index, not type name
3. Register ViewWidget aliases by type, not by string

+ Add image block to vtkResourceMultiBlockSource's output.
+ Add a slice representation to the first image block
  of SMTK's representation of a resource.
+ Add domain to slice property to create sliders in the UI
  for a demo.
+ Create a color map for the slice representations.
  We assume that if an SMTK resource includes image data,
  the resource will provide us with a color map for it.
+ Add missing ParaView dependencies.
+ Remove image slice properties (slice sliders) from the
  property panel for SMTK representations until there is a
  way to add properties dynamically based on the available
  images to be shown.

Replace use of smtk_plugin_add_ui_view everywhere with Registrars.
Remove the qt/ParaView interface that used to register views.

First teeny part of view factory redesign.

These changes were made to help simplify/cleanup the qtView infrastructure. There were several places where onShowCategory() was being called in order to update the UI. This resulted in confusion as to the role of the method. In many cases these calls have been replaced with updateUI.

qtBaseView::updateViewUI - has been removed. It was not being used.
qtBaseAttributeView::updateAttributeData - has been removed. This method's role was to update the attribute content of a View. You should now call updateUI() instead.
qtBaseAttributeView no longer overrides updateUI()

Also changed setAdvanceLevel(int) method to no longer delete children Views in a qtGroupView

- Calling updateItemData method would create a new set of widget (without deleting the original set)
instead of simply updating what is there.

Addresses issue #287

When a widget is used to update an attribute item's value,
this triggers a "Signal" operation. In turn, the base
pqSMTKAttributeItemWidget class's operation observer was
responding by asking the widget to update widget values from
the item. This made interaction via the widget overtly unfriendly.
Don't do that.