[Repository Listing] / [Slicer3] / branches / Slicer4-EMSegment
 

Index of /branches/Slicer4-EMSegment

Directory revision: 17141 (of 17141)
Sticky Revision:


Name Rev. Age Author Last log entry
Parent Directory
       
View directory contents AMF
 17139  2 weeks  hjohnson  ENH: Remove deprecated use of the register keyword Slicer-bld/EMSegment/AMF/vtkMinHeap.h:235:5: warning: 'register' storage class specifier is deprecated and incompatible with C++1z       [-Wdeprecated-register]     register int  down;     ^~~~~~~~~
View directory contents Algorithm
 17135  6 weeks  msmolens  COMP: Fix inconsistent-missing-override warnings This commit fixes warnings like the following: Slicer-0-build/EMSegment/MRML/vtkMRMLEMSNode.h:27:8: warning: 'PrintSelf' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] void PrintSelf(ostream& os, vtkIndent indent); ^ Slicer-0/Libs/MRML/Core/vtkMRMLNode.h:144:8: note: overridden virtual function is here void PrintSelf(ostream& os, vtkIndent indent) VTK_OVERRIDE; ^ From: Hina Shah <hina.shah@kitware.com>
View directory contents CMake
 17112  22 months  pohl  ENH: added vtkImageClipAutomatic to Slicer4-EMSegment and included functionality in EMSegmentCommandLine
View directory contents CommandLineApplication
 17140  2 weeks  jcfr  COMP: Setting CMP0020 to NEW to remove build warnings
View directory contents ImageFilters
 17135  6 weeks  msmolens  COMP: Fix inconsistent-missing-override warnings This commit fixes warnings like the following: Slicer-0-build/EMSegment/MRML/vtkMRMLEMSNode.h:27:8: warning: 'PrintSelf' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] void PrintSelf(ostream& os, vtkIndent indent); ^ Slicer-0/Libs/MRML/Core/vtkMRMLNode.h:144:8: note: overridden virtual function is here void PrintSelf(ostream& os, vtkIndent indent) VTK_OVERRIDE; ^ From: Hina Shah <hina.shah@kitware.com>
View directory contents MRML
 17135  6 weeks  msmolens  COMP: Fix inconsistent-missing-override warnings This commit fixes warnings like the following: Slicer-0-build/EMSegment/MRML/vtkMRMLEMSNode.h:27:8: warning: 'PrintSelf' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] void PrintSelf(ostream& os, vtkIndent indent); ^ Slicer-0/Libs/MRML/Core/vtkMRMLNode.h:144:8: note: overridden virtual function is here void PrintSelf(ostream& os, vtkIndent indent) VTK_OVERRIDE; ^ From: Hina Shah <hina.shah@kitware.com>
View directory contents Qt
 17138  3 weeks  jcfr  COMP: Fix VTK8 python wrapping adding missing include dirs
View directory contents Registration
 17135  6 weeks  msmolens  COMP: Fix inconsistent-missing-override warnings This commit fixes warnings like the following: Slicer-0-build/EMSegment/MRML/vtkMRMLEMSNode.h:27:8: warning: 'PrintSelf' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] void PrintSelf(ostream& os, vtkIndent indent); ^ Slicer-0/Libs/MRML/Core/vtkMRMLNode.h:144:8: note: overridden virtual function is here void PrintSelf(ostream& os, vtkIndent indent) VTK_OVERRIDE; ^ From: Hina Shah <hina.shah@kitware.com>
View directory contents Tasks
 17135  6 weeks  msmolens  COMP: Fix inconsistent-missing-override warnings This commit fixes warnings like the following: Slicer-0-build/EMSegment/MRML/vtkMRMLEMSNode.h:27:8: warning: 'PrintSelf' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] void PrintSelf(ostream& os, vtkIndent indent); ^ Slicer-0/Libs/MRML/Core/vtkMRMLNode.h:144:8: note: overridden virtual function is here void PrintSelf(ostream& os, vtkIndent indent) VTK_OVERRIDE; ^ From: Hina Shah <hina.shah@kitware.com>
View directory contents Tcl
 17099  2 years  pohl  STYLE: Changed output to make it easier readable
View directory contents Testing
 17141  2 days  lassoan  BUG: Fixed test error due to changed selection node Selection node has now a activePlotChartID member.
View file contents CMakeLists.txt
 17134  7 weeks  jcfr  COMP: Fix warning removing explicit setting of CMake policy CMP0017. Setting of CMP0017 to OLD is not needed. This commit addresses the following warning reported when using CMake 3.9.0: See https://github.com/Slicer/Slicer/pull/765
View file contents README
 17042  3 years  jcfr  COMP: Create Slicer4-EMSegment branch for current development. Following discussion with Kilian Pohl, we agreed on creating a dedicated branch to support the update of the module so that it build and run against Slicer4. It means that code pushed on [1] is expected for maintainance of the EMSegment so that it build and run against Slicer3. On the other hand, code pushed on [2] is non expected to be backward compatible with Slicer3 and is done to ensure that EMSegment build and run against Slicer4. [1] http://svn.slicer.org/Slicer3/trunk/Modules/EMSegment [2] http://svn.slicer.org/Slicer3/branches/Slicer4-EMSegment For reference, the following command was used: svn copy http://svn.slicer.org/Slicer3/trunk/Modules/EMSegment \ http://svn.slicer.org/Slicer3/branches/Slicer4-EMSegment
View file contents vtkEMSegment.h
 17045  3 years  finetjul  ENH: Add VTK 6 support
View file contents vtkEMSegmentConfigure.h.in
 17042  3 years  jcfr  COMP: Create Slicer4-EMSegment branch for current development. Following discussion with Kilian Pohl, we agreed on creating a dedicated branch to support the update of the module so that it build and run against Slicer4. It means that code pushed on [1] is expected for maintainance of the EMSegment so that it build and run against Slicer3. On the other hand, code pushed on [2] is non expected to be backward compatible with Slicer3 and is done to ensure that EMSegment build and run against Slicer4. [1] http://svn.slicer.org/Slicer3/trunk/Modules/EMSegment [2] http://svn.slicer.org/Slicer3/branches/Slicer4-EMSegment For reference, the following command was used: svn copy http://svn.slicer.org/Slicer3/trunk/Modules/EMSegment \ http://svn.slicer.org/Slicer3/branches/Slicer4-EMSegment
View file contents vtkEMSegmentLogic.cxx
 17131  2 months  msmolens  ENH: Call InitializeObjectBase() in New() methods In VTK8 it's necessary for New() methods to call InitializeObjectBase() on the new object for proper tracking with vtkDebugLeaks. The standard macros (vtkStandardNewMacro, vtkObjectFactoryNewMacro) handle this. For those classes that don't use the macros, add calls to InitializeObjectBase(). Continue to support earlier versions of VTK by wrapping calls to InitializeObjectBase() in checks for the preprocessor define VTK_HAS_INITIALIZE_OBJECT_BASE. It's possible that many of these implementations could be simplified by using the standard macros. See also: - https://github.com/Kitware/VTK/commit/e5c793dbdf87e838bb2b60c6a5905ced0e5548f9 - http://public.kitware.com/pipermail/vtk-developers/2016-September/034332.html
View file contents vtkEMSegmentLogic.h
 17135  6 weeks  msmolens  COMP: Fix inconsistent-missing-override warnings This commit fixes warnings like the following: Slicer-0-build/EMSegment/MRML/vtkMRMLEMSNode.h:27:8: warning: 'PrintSelf' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] void PrintSelf(ostream& os, vtkIndent indent); ^ Slicer-0/Libs/MRML/Core/vtkMRMLNode.h:144:8: note: overridden virtual function is here void PrintSelf(ostream& os, vtkIndent indent) VTK_OVERRIDE; ^ From: Hina Shah <hina.shah@kitware.com>
View file contents vtkEMSegmentMRMLManager.cxx
 17131  2 months  msmolens  ENH: Call InitializeObjectBase() in New() methods In VTK8 it's necessary for New() methods to call InitializeObjectBase() on the new object for proper tracking with vtkDebugLeaks. The standard macros (vtkStandardNewMacro, vtkObjectFactoryNewMacro) handle this. For those classes that don't use the macros, add calls to InitializeObjectBase(). Continue to support earlier versions of VTK by wrapping calls to InitializeObjectBase() in checks for the preprocessor define VTK_HAS_INITIALIZE_OBJECT_BASE. It's possible that many of these implementations could be simplified by using the standard macros. See also: - https://github.com/Kitware/VTK/commit/e5c793dbdf87e838bb2b60c6a5905ced0e5548f9 - http://public.kitware.com/pipermail/vtk-developers/2016-September/034332.html
View file contents vtkEMSegmentMRMLManager.h
 17135  6 weeks  msmolens  COMP: Fix inconsistent-missing-override warnings This commit fixes warnings like the following: Slicer-0-build/EMSegment/MRML/vtkMRMLEMSNode.h:27:8: warning: 'PrintSelf' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] void PrintSelf(ostream& os, vtkIndent indent); ^ Slicer-0/Libs/MRML/Core/vtkMRMLNode.h:144:8: note: overridden virtual function is here void PrintSelf(ostream& os, vtkIndent indent) VTK_OVERRIDE; ^ From: Hina Shah <hina.shah@kitware.com>
View file contents vtkEMSegmentWin32Header.h
 17042  3 years  jcfr  COMP: Create Slicer4-EMSegment branch for current development. Following discussion with Kilian Pohl, we agreed on creating a dedicated branch to support the update of the module so that it build and run against Slicer4. It means that code pushed on [1] is expected for maintainance of the EMSegment so that it build and run against Slicer3. On the other hand, code pushed on [2] is non expected to be backward compatible with Slicer3 and is done to ensure that EMSegment build and run against Slicer4. [1] http://svn.slicer.org/Slicer3/trunk/Modules/EMSegment [2] http://svn.slicer.org/Slicer3/branches/Slicer4-EMSegment For reference, the following command was used: svn copy http://svn.slicer.org/Slicer3/trunk/Modules/EMSegment \ http://svn.slicer.org/Slicer3/branches/Slicer4-EMSegment
View file contents vtkSlicerCommonInterface.cxx
 17131  2 months  msmolens  ENH: Call InitializeObjectBase() in New() methods In VTK8 it's necessary for New() methods to call InitializeObjectBase() on the new object for proper tracking with vtkDebugLeaks. The standard macros (vtkStandardNewMacro, vtkObjectFactoryNewMacro) handle this. For those classes that don't use the macros, add calls to InitializeObjectBase(). Continue to support earlier versions of VTK by wrapping calls to InitializeObjectBase() in checks for the preprocessor define VTK_HAS_INITIALIZE_OBJECT_BASE. It's possible that many of these implementations could be simplified by using the standard macros. See also: - https://github.com/Kitware/VTK/commit/e5c793dbdf87e838bb2b60c6a5905ced0e5548f9 - http://public.kitware.com/pipermail/vtk-developers/2016-September/034332.html
View file contents vtkSlicerCommonInterface.h
 17071  3 years  pohl  STYLE: Removed KWWidgets as it is not part of Slicer 4
View file contents vtkSlicerEMSegmentModuleLogicExport.h
 17042  3 years  jcfr  COMP: Create Slicer4-EMSegment branch for current development. Following discussion with Kilian Pohl, we agreed on creating a dedicated branch to support the update of the module so that it build and run against Slicer4. It means that code pushed on [1] is expected for maintainance of the EMSegment so that it build and run against Slicer3. On the other hand, code pushed on [2] is non expected to be backward compatible with Slicer3 and is done to ensure that EMSegment build and run against Slicer4. [1] http://svn.slicer.org/Slicer3/trunk/Modules/EMSegment [2] http://svn.slicer.org/Slicer3/branches/Slicer4-EMSegment For reference, the following command was used: svn copy http://svn.slicer.org/Slicer3/trunk/Modules/EMSegment \ http://svn.slicer.org/Slicer3/branches/Slicer4-EMSegment
 

Properties

Name Value
svn:mergeinfo /branches/Slicer4-EMSegment-LabelMapVolumeNode:17091

  Subversion  TortoiseSVN  ViewVC