Documentation/Nightly/Developers/Tutorials/MigrationGuide/VTK7-Qt4-to-VTK8-Qt5 - Revision history

JChris.FillionR at 18:04, 15 October 2018

2018-10-15T18:04:44Z

2018-10-15T18:04:07Z

2018-08-30T23:06:11Z

2018-08-30T22:58:46Z

Add python version on how to workaround setResizeMode error in qt5

2018-08-30T22:47:56Z

2018-08-30T22:43:54Z

2018-08-30T22:29:30Z

2018-02-13T16:10:27Z

Slicer module initialization

2018-02-13T16:10:00Z

Added note about using startup completed signal instead of singleshot timer

2018-01-31T21:39:08Z

Undo revision 58344 by JChris.FillionR (talk)

@@ Line 1: / Line 1: @@
 <noinclude>__TOC__</noinclude>
-==Transition from VTK7-Qt4 to VTK9-Qt5==
+==Transition from VTK7-Qt4 to VTK8-Qt5==
 This section lists categories of code changes necessary to build and run Slicer with VTK 8.0 and Qt5. Each category has a short description, a suggested upgrade path, and references to relevant commits (TBD once merged).
@@ Line 455: / Line 455: @@
 For example, see https://github.com/SlicerIGT/SlicerIGT/pull/155/commits/2f866ea8872435b9a3a7382dd0549231da00406f
-===VTK9: Signature of vtkFSLookupTable::MapValue updated ===
+===VTK 8.2: Signature of vtkFSLookupTable::MapValue updated ===
 The signature of the function was updated in [https://github.com/Kitware/VTK/commit/43f6ee3 Kitware/VTK@43f6ee3]

@@ Line 283: / Line 283: @@
    from packaging import version
    def _setSectionResizeMode(header, *args, **kwargs):
      """ To be compatible with Qt4 and Qt5 """
@@ Line 289: / Line 290: @@
      else:
        header.setSectionResizeMode(*args, **kwargs)
 ===VTK8: Use hierarchy files for VTK Python wrapping===

@@ Line 279: / Line 279: @@
      headerView->setSectionResizeMode(FileColumn, QHeaderView::Stretch);
    #endif
 ===VTK8: Use hierarchy files for VTK Python wrapping===

@@ Line 1: / Line 1: @@
 <noinclude>__TOC__</noinclude>
-==Transition from VTK7-Qt4 to VTK8-Qt5==
+==Transition from VTK7-Qt4 to VTK9-Qt5==
 This section lists categories of code changes necessary to build and run Slicer with VTK 8.0 and Qt5. Each category has a short description, a suggested upgrade path, and references to relevant commits (TBD once merged).

@@ Line 1: / Line 1: @@
 <noinclude>__TOC__</noinclude>
-==Migration guide: Transition from VTK7-Qt4 to VTK8-Qt5==
+==Transition from VTK7-Qt4 to VTK8-Qt5==
 This section lists categories of code changes necessary to build and run Slicer with VTK 8.0 and Qt5. Each category has a short description, a suggested upgrade path, and references to relevant commits (TBD once merged).

← Older revision	Revision as of 18:04, 15 October 2018
(No difference)

← Older revision		Revision as of 22:29, 30 August 2018
Line 1:		Line 1:
−	== Migration ~~Guide~~ ==	+	<noinclude>__TOC__</noinclude>
		+	==Migration guide: Transition from VTK7-Qt4 to VTK8-Qt5==

	This section lists categories of code changes necessary to build and run Slicer with VTK 8.0 and Qt5. Each category has a short description, a suggested upgrade path, and references to relevant commits (TBD once merged).		This section lists categories of code changes necessary to build and run Slicer with VTK 8.0 and Qt5. Each category has a short description, a suggested upgrade path, and references to relevant commits (TBD once merged).

@@ Line 455: / Line 455: @@
 Update code to use `const` keyword. For example, see [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=26708 r26708]
-===Slicer module initialization===
+===Slicer scripted module initialization steps after application startup===
 In Slicer 4.8 and earlier versions, those module initialization steps that required application startup completed, often were called using a singleshot timer, because timer events were only processed after the application startup was completed. In Slicer 4.9, some event processing is performed before the application startup is completed, therefore instead of relying on a timer, the application's ''startupCompleted()'' signal must be used.

← Older revision		Revision as of 16:10, 13 February 2018
Line 454:		Line 454:

	Update code to use `const` keyword. For example, see [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=26708 r26708]		Update code to use `const` keyword. For example, see [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=26708 r26708]
		+
		+	===Slicer module initialization===
		+
		+	In Slicer 4.8 and earlier versions, those module initialization steps that required application startup completed, often were called using a singleshot timer, because timer events were only processed after the application startup was completed. In Slicer 4.9, some event processing is performed before the application startup is completed, therefore instead of relying on a timer, the application's ''startupCompleted()'' signal must be used.
		+
		+	Replace line like:
		+
		+	qt.QTimer.singleShot(0, self.myAdditionalInitializationSteps)
		+
		+	with:
		+
		+	slicer.app.connect("startupCompleted()", self.myAdditionalInitializationSteps)

← Older revision		Revision as of 21:39, 31 January 2018
Line 425:		Line 425:
	VTK_MODULE_INIT(vtkSlicer<NameOfModule>ModuleMRMLDisplayableManager)		VTK_MODULE_INIT(vtkSlicer<NameOfModule>ModuleMRMLDisplayableManager)

		+
		+	<b>Solution (part 2 - maintaining backward compatibility with Slicer 4.8):</b>
		+
		+	#include <vtkSlicerVersionConfigure.h> // For Slicer_VERSION_MAJOR, Slicer_VERSION_MINOR
		+
		+
		+	[...]
		+
		+	// DisplayableManager initialization
		+	#if Slicer_VERSION_MAJOR == 4 && Slicer_VERSION_MINOR >= 9
		+	#include <vtkAutoInit.h>
		+	VTK_MODULE_INIT(vtkSlicer<NameOfModule>ModuleMRMLDisplayableManager)
		+	#endif

	For example, see https://github.com/SlicerIGT/SlicerIGT/pull/155/commits/2f866ea8872435b9a3a7382dd0549231da00406f		For example, see https://github.com/SlicerIGT/SlicerIGT/pull/155/commits/2f866ea8872435b9a3a7382dd0549231da00406f