1. 24 Jun, 2012 3 commits
  2. 23 Jun, 2012 1 commit
  3. 20 Jun, 2012 1 commit
  4. 18 Jun, 2012 1 commit
  5. 17 Jun, 2012 1 commit
  6. 16 Jun, 2012 2 commits
  7. 15 Jun, 2012 2 commits
  8. 14 Jun, 2012 2 commits
    • finetjul's avatar
      STYLE: Update vtkSlicerVolumeRenderingLogic documentation · ea9b1ec6
      finetjul authored
      git-svn-id: http://svn.slicer.org/Slicer4/trunk@20365 3bd1e089-480b-0410-8dfb-8563597acbee
      ea9b1ec6
    • finetjul's avatar
      ENH: Redesign ModifiedSinceRead · be2d5e78
      finetjul authored
      ModifiedSinceRead can no longer be set externally, it's the nodes themselves that computes it based on the last time the data was stored and on the modifications.
      ModifiedSinceRead is no longer a vtkMRMLNode property but a vtkMRMLStorableNode property.
      The storage nodes have been cleaned-up (factorized) in the process.
      At exit time, the scene is checked to see if it has been modified or if its storable nodes have been modified since read/write.
      
      Some other changes:
      Removed vtkMRMLModelNode::GetDefaultWriteFileExtension() it is a duplicate from vtkMRMLModelStorageNdoe::GetDefaultWriteFileExtension()
      Removed vtkMRMLColorNode::AddColorName() as it is not used and increase code complexity
      Removed vtkMRMLAnnotation*StorageNode::WriteData(vtkMRMLNode* refNode) as it was doing the same than vtkMRMLAnnotationStorageNode::WriteData(vtkMRMLNode* refNode)
      
      Remaining issues:
      The check on the modified scene is not perfect and can be fine tuned.
      The loading of annotations are marking the nodes as ModifiedSinceRead but it shouldn't.
      The loading of a vtkMRMLVolumePropertyNode from within a scene load incorrectly marks the node as ModifiedSinceRead
      
      
      git-svn-id: http://svn.slicer.org/Slicer4/trunk@20360 3bd1e089-480b-0410-8dfb-8563597acbee
      be2d5e78
  9. 13 Jun, 2012 2 commits
  10. 11 Jun, 2012 1 commit
  11. 08 Jun, 2012 1 commit
  12. 07 Jun, 2012 2 commits
  13. 04 Jun, 2012 1 commit
  14. 01 Jun, 2012 1 commit
    • finetjul's avatar
      BUG: Fix vtkMRMLModelNode::SetAndObservePolyData when display node is not yet set and observed · a8c672e1
      finetjul authored
      Depending on when the display node was added into the scene/model, the polydata was not necessarily propagated to the display node.
      vtkMRMLModelNode::UpdateScene() was removed because the polydata is now set to the display nodes by vtkMRMLModelNode::OnDisplayNodeAdded whenever a display node is added/retrieved
      vtkMRMLModelNode::ProcessMRMLEvents is modified because there was a side effect in vtkMRMLModelNode::SetAndObservePolyData: the polydata was first set to the display nodes that fired a modified event observed by the model node which was resetting the polydata to its own old value (not yet set in SetAndObservePolyData) cancelling the first set.
      Add utility method vtkSlicerModelsLogic::AddModel(vtkPolyData*) to shorten the creation of model node and display node.
      
      git-svn-id: http://svn.slicer.org/Slicer4/trunk@20306 3bd1e089-480b-0410-8dfb-8563597acbee
      a8c672e1
  15. 30 May, 2012 1 commit
  16. 28 May, 2012 1 commit
  17. 26 May, 2012 1 commit
  18. 25 May, 2012 2 commits
  19. 24 May, 2012 2 commits
  20. 23 May, 2012 3 commits
  21. 22 May, 2012 1 commit
  22. 21 May, 2012 2 commits
  23. 20 May, 2012 4 commits
  24. 18 May, 2012 2 commits