1. 27 Jun, 2012 1 commit
    • Halla Rempt's avatar
      Show selected rows in the layer docker in Windows styles · 58d4edea
      Halla Rempt authored
      Adding m_wdgLayerBox->listLayers->setSelectionBehavior(QAbstractItemView::SelectRows);
      makes the windows styles paint the selection background for the whole
      row. Oxygen-based styles don't need that, apparently, but it cannot
      hurt.
      
      BUG:134821
      58d4edea
  2. 24 May, 2012 1 commit
  3. 16 May, 2012 1 commit
  4. 07 May, 2012 1 commit
  5. 02 Mar, 2012 1 commit
  6. 04 Feb, 2012 2 commits
  7. 03 Feb, 2012 2 commits
    • Dmitry Kazakov's avatar
      Fixed Drag & Drop in the Layer Box. Now it works perfectly! · add6b81b
      Dmitry Kazakov authored
      Yeah, like in all the other applications!
      
      BUG:292669
      BUG:292667
      add6b81b
    • Dmitry Kazakov's avatar
      Fixed managing selection masks which are children of the root node · dfc19c96
      Dmitry Kazakov authored
      Now the mapping between KisNodeDummy and QModelIndex is done by
      classes KisModeIndexConverter and KisModelIndexConverterShowAll.
      They represent two options available to the user: normal mode and
      mode when the root layer is visible.
      
      This is the last commit in a series of refactorings for KisNodeModel.
      Now there should be no known crashes or bugs. So if you see one, do
      not hesitate to report! ;)
      
      My plan is the following:
      1) I'm pushing it to my branch.
      2) Then I'll fix drag-and-drop (it is unrelated to the refactorings)
      3) Then I'll make a call for testing both of the features, to
         save the time of artists ;)
      
      BUG:291271
      BUG:290708
      dfc19c96
  8. 31 Jan, 2012 1 commit
    • Dmitry Kazakov's avatar
      Moved managing dummies out of KisShapeController · 6eb629cf
      Dmitry Kazakov authored
      Now we have a separate class that manages dummies/shapes. It is
      named KisDummiesFacadeBase. KisShapeController is derived from
      this class. That allowed us to break dependency of KisNodeModel from
      KisShapeController. Now it depends on KisDummiesFacadeBase, so we can
      easily create one more KisNodeModel in the Bumpmap filter.
      6eb629cf
  9. 29 Jan, 2012 1 commit
    • Dmitry Kazakov's avatar
      A huge refactoring for KisNodeModel · 040a948d
      Dmitry Kazakov authored
      Now the model doesn't depend on the hierarchy of the image. It uses
      the hierarchy of the dummies stored in KiShapeController instead.
      
      Some bullet points:
      1) KisShapeController connects to the image and forwards the node
      addition/removal signals for other recievers
      2) KisNodeModel is connected to the KisShapeController and listens
      to the forwarded signals. It follows that it doesn't depend on the image
      directly, so there are no problems with multithreading.
      2.5) KisNodeModel does not depend on sigLayersChanged() anymore.
      3) KisShapeController manages when a node should be activated. It emits
      the signal sigActivateNode(KisNodeSP) which is processed by the
      KisNodeManager. It solved many problems at once. First, we needn't
      workaround moving of nodes (KisNodeManager::Private::activeBeforeMove).
      Second we are able to deprecate KisNodeManager::activateNode() now. (It'll be
      done in one of next commmits).
      4) Fixed KisNodeFacade::lowerNode(). Now newly activated node depends on the node
      which is added in the end of the operation, so we should move exactly the node
      which was requested.
      5) A small refactoring for KisLayerBox is done. It was discussed with Boud on irc.
      
      
      Not yet fixed issues:
      1) I had to disable Bumpmap filter temporarily, because it didn't
      compile with changed KisNodeModel. It'll be fixed in the following commits.
      2) When loading an image with many layers KisLayerBox does not scroll to
      the active layer.
      040a948d
  10. 31 Oct, 2011 1 commit
    • Torio Mlshi's avatar
      Return support for clone layers of group layers · c5667707
      Torio Mlshi authored
      Also add checking if clone layer could be moved to group layer not
      causing cyclic behaviour. This checking is recursive and so any case
      when clone layer depends on groups or another clones could be checked.
      c5667707
  11. 12 Aug, 2011 1 commit
  12. 02 Aug, 2011 1 commit
  13. 01 Aug, 2011 1 commit
  14. 25 Jul, 2011 1 commit
  15. 24 Jul, 2011 2 commits
    • Halla Rempt's avatar
      Implement node conversion, step 1 · 1f4a9a81
      Halla Rempt authored
      Basic design: remove the node creation dropdown button and add a button
      for every node type. The buttons are drop targets, and send out a signal
      that can be used to create/create & replace a node based on data from the
      dropped node.
      1f4a9a81
    • Halla Rempt's avatar
      Hide KisLayerManager behind KisNodeManager · 39e767a0
      Halla Rempt authored
      KisLayerManager is now no longer public api. But sometimes krita needs
      to now the active layer even if the active node is a mask, for instance
      for colorspace selection. So expose that through KisNodeManager.
      
      KisNodeManager/KisMaskManage/KisLayerManager still need a bit of an api
      cleanup.
      39e767a0
  16. 08 Jul, 2011 2 commits
    • José Luis Vergara's avatar
      Re-add menu entries to KisLayerBox that were relevant to the current layer · c77d07ad
      José Luis Vergara authored
      o The Mask-adding actions were restored to the menu since it makes sense
      to right click on a layer to add a mask to it.
      
      BUG:275764
      c77d07ad
    • José Luis Vergara's avatar
      Remove unnecessary clutter from the KisLayerBox menu · 6c39c98e
      José Luis Vergara authored
      o Commands to change the layer's individual properties were removed: there are
      icons for that.
      o Commands to add new layers were removed: the add layer button is there for that,
      and there is no need to right click on a layer to add a new layer.
      o Commands to delete, duplicate or merge the layer down were presented: there are
      icons to do that (except merge layer down), however, right clicking on a layer to
      remove it or duplicate it makes sense, unlike right clicking on a layer to add a new one.
      
      BUG:275764
      6c39c98e
  17. 07 Jul, 2011 1 commit
  18. 01 Jul, 2011 2 commits
  19. 25 Jun, 2011 7 commits
  20. 24 Jun, 2011 3 commits
  21. 21 Jun, 2011 1 commit
  22. 16 Jun, 2011 1 commit
  23. 14 Jun, 2011 1 commit
  24. 11 Jun, 2011 1 commit
  25. 03 Jun, 2011 2 commits
  26. 22 May, 2011 1 commit