1. 12 Jan, 2019 2 commits
  2. 07 Dec, 2018 1 commit
  3. 02 Jul, 2018 1 commit
  4. 14 Jun, 2018 1 commit
    • Bob Obara's avatar
      ENH: Dealing with displaying empty views · b188e1b4
      Bob Obara authored
      View can be empty for a variety of reasons:
      - ModelEntityAttribute Views and Attribute Views with no definitions due to filter by advance and/or category
      - Instance Views with no attribute items due to filtering by advance and/or category
      
      The problem is when displaying children views in a tiled group view, the name of the empty view is displayed with no content.
      
      The solution was to add the concept of isEmpty to the qtViews and qtAttribute
      b188e1b4
  5. 03 May, 2018 1 commit
    • Bob Obara's avatar
      ENH: Supporting new ModelEntityView · 48cd6cfc
      Bob Obara authored
      The new view lists the appropriate model entities and provides the ability to create and assign
      unique attributes to them. The format is simular to the Attribute View with the following additional
      view attributes:
      
      - Type = "ModelEntity"
        * - Col1Header - The name to be used as the column 1 header if the attribute
        * does not exist "Model Entity" is displayed
        * - Col2Header - The name to be used as the column 2 header if the attribute
        * does not exist "Type" is displayed
        * - NoValueLabel - The label to be used to indicate that a model entity does not have an appropriate attribute associated with it
      
      This commit also includes changing attributes() method that return attribute UUIDs to attributeIDs() and
      added a new EntityRef::attributes(attribute::DefininitionPtr def) that returns the attribute are based on
      def (or derived from it)
      
      Also made qtBaseView a friend of the qUIManager so derived views have access to invokeEntitiesSelected method
      48cd6cfc
  6. 21 Mar, 2018 1 commit
  7. 19 Feb, 2018 1 commit
  8. 28 Nov, 2017 1 commit
    • Bob Obara's avatar
      BUG: Fixed issue related to Selection Manager and qtModelItem · 8708c012
      Bob Obara authored
      The problem was that by default every time a qtModelItem was displayed it would
      update itself based on the curent selection.  While this behavior is correct for
      Operators it is not correct for defining a Simulation.
      
      A mode has been added to qtViews, qtItems and qtAttribute to indicate if this
      behavior is desirable - note that the class can still choose to ignore this option and
      use the older manual mode - for example if an attrbute had two model enity items that
      shared the same selection masks
      8708c012
  9. 19 Nov, 2017 1 commit
  10. 23 Aug, 2017 1 commit
  11. 27 Jul, 2017 1 commit
  12. 14 Jun, 2017 1 commit
  13. 26 Apr, 2017 1 commit
  14. 29 Mar, 2017 1 commit
  15. 05 Jan, 2017 1 commit
    • Bob Obara's avatar
      ENH: Added new qtOperatorView class · 2ef78dee
      Bob Obara authored
      This class creates a default UI for an operator.  It determines
      when the operation can be applied by changing teh validity of the
      underlying attribute as well as preventing the same operation from
      being accendently applied multiple times.
      
      - ALSO Fixed bug in model entity association which was causing
      model entities to be inserted in the item multiple times
      2ef78dee
  16. 18 May, 2016 2 commits
  17. 22 Feb, 2016 1 commit
  18. 01 Feb, 2016 1 commit
  19. 17 Dec, 2015 1 commit
  20. 28 Aug, 2015 1 commit
    • Bob Obara's avatar
      ENH: Removing concept of Root View for GUIs · 5269895c
      Bob Obara authored
      Also added the ability to indicate if filter by either
      advance level or category is required.
      
      Also made the ability to display the access level for each item optional
      5269895c
  21. 02 Jun, 2015 1 commit
  22. 24 May, 2015 1 commit
  23. 04 May, 2015 1 commit
  24. 21 Apr, 2015 1 commit
    • David Thompson's avatar
      Progress on #85 (consistent target + option names). · eaf24846
      David Thompson authored
      This patch includes the following changes:
      
      + Eliminate a shiboken warning (do not wrap cJSON methods).
      + Fix a stupid mistake causing a warning in ExportJSON.
      + A scripted rename. Ran this command:
      
            find smtk/bridge -type f -exec vim -S /path/to/vscr {} \;
      
        where `vscr` contained
      
            %s/SMTKSessionExodusExports/Exports/g
            %s/SMTKSessionExodus/smtkExodusSession/g
            %s/SMTKSESSIONEXODUS_EXPORT/SMTKEXODUSSESSION_EXPORT/g
            %s/discreteSessionExports/Exports/g
            %s/SMTKRemoteExports/Exports/g
            %s/SMTKRemote/smtkRemoteSession/g
            %s/SMTKREMOTE_EXPORT/SMTKREMOTESESSION_EXPORT/g
            wq
      + Another scripted rename:
      
            find smtk/extension -type f -exec vim -S /path/to/vscr {} \;
      
        where `vscr` is a vim script containing:
      
            %s/QtSMTKExports.h/Exports.h/g
            %s/QTSMTK_EXPORT/SMTKQTEXT_EXPORT/g
            %s/vtkSMTKModule/smtkVTKExtModule/g
            %s/vtkSMTKExports/smtkVTKExtExports/g
            %s/VTKSMTK_EXPORT/SMTKVTKEXT_EXPORT/g
            %s/vtkSMTK/smtkVTKExt/g
            wq
      
      + Add VTK-style Python wrapping to the classes in vtkSMTKExt
        (which cannot be named smtkVTKExt because of VTK's build system).
        This should close #97.
      + Fixes to get things building again.
      eaf24846
  25. 09 Apr, 2015 1 commit
    • Yumin Yuan's avatar
      Add APIs to automatically associate operator model entity item. · fb72acba
      Yumin Yuan authored
      When a model operator's UI is launched, we want the ModelEntityItem(s) in
      the operator specifiction to be automatically associated with the current selection
      in the modelView, if the entity flags match with the item's entity mask. If we did not
      find any suitable matches in the children of the selected entities, we will also search
      the parents. For example, if a Face is selected, but the ModelEnityItem is requiring a model,
      we will search up the tree and associated the item with the model owning the face.
      fb72acba
  26. 16 Feb, 2015 1 commit
  27. 26 Sep, 2014 1 commit
  28. 24 Sep, 2014 2 commits
  29. 22 May, 2014 1 commit
  30. 20 May, 2014 1 commit
  31. 14 May, 2014 1 commit
  32. 30 Apr, 2014 1 commit
    • Yumin Yuan's avatar
      Made label lenth a bit smarter for instanced view. · cf2ce4bd
      Yumin Yuan authored
      The attribute item labels vary quite a bit, and a fixed global label length does not always look so well, and wastes a lot of horizontal space if the labels are shorter than the global length, though they do line up nicely. Some logic is added so that we go through the attribute items first to find the longest label as a hint combined with the global length to decide the appropriate length for labels.
      cf2ce4bd
  33. 09 Apr, 2014 1 commit
  34. 03 Apr, 2014 1 commit
    • Yumin Yuan's avatar
      Added modified item to ui signal. · dc6a6b1d
      Yumin Yuan authored
      The consumer of the signal now knows about the items being modified, besides the view panel. This is very useful for flagging attributes that are referencing changed attributes. Eventually, once we have signal-callbacks mechanism implemented inside attribute system, these type of interactions will be easier to deal with.
      dc6a6b1d
  35. 31 Mar, 2014 1 commit
  36. 10 Feb, 2014 1 commit
    • Yumin Yuan's avatar
      Removed UIManager singleton pattern. · ed4e8521
      Yumin Yuan authored
      The singleton pattern of UIManager was removed so that applications can
      create as many UIManagers as they want. The singleton pattern was
      inherited from SimBuilder3.0, but since now the uiManager is part of the
      smtk library, the pattern isn't desired anymore. However, applications can
      still use singleton pattern if they wrapp the uiManager with another
      class.
      ed4e8521
  37. 17 Oct, 2013 1 commit