Documentation/4.1/Developers/Tutorials/QtDesigner - Revision history

UpdateBot: Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-06-14T07:30:19Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

Finetjul: /* Build Slicer */

2012-06-28T16:48:11Z

Build Slicer

Finetjul: /* Qt Designer requirements */

2012-06-28T16:39:49Z

Qt Designer requirements

Finetjul: /* Build Slicer */

2012-06-28T16:37:46Z

Build Slicer

JChris.FillionR: /* Straight to the point */

2012-06-08T16:17:11Z

Straight to the point

JChris.FillionR at 16:16, 8 June 2012

2012-06-08T16:16:34Z

JChris.FillionR: /* Running Qt Designer with the correct environment variables */

2012-06-08T15:23:34Z

Running Qt Designer with the correct environment variables

JChris.FillionR: 4.0 -> 4.1

2012-04-12T04:42:04Z

4.0 -> 4.1

New page

Back to [[Documentation/{{documentation/version}}/Developers|Developers Information]]←

=Using custom widgets in Qt Designer=
==Straight to the point==
*Windows
**Compile Slicer in Release mode OR build Qt in Debug
*All
<pre>
cd Slicer-build;
./Slicer --designer
</pre>

==Qt Designer requirements==
In order to have the CTK and MRML widgets in Qt Designer, Qt Designer offers 2 options:
*the first (not detailed here) is to copy (or symlink) the CTK and MRML plugin libraries into %QT_DIR%/plugins/designer,
*the second is to set the environment variable <code>QT_PLUGIN_PATH</code> to the directory Slicer-build/bin containing the subdirectory designer with the plugin libraries. 
'''Note:''' Qt requires that the directory containing the designer plugins is named "designer". 
=== Windows notes ===
On Windows, Qt Designer can only load plugins that have been compiled in the same build mode than Qt Designer. For example, if Qt is built in Debug mode, the plugins must also be built in Debug mode to be loaded by Qt Designer. 
If Qt is configured to build in both debug and release modes, Qt Designer is built in release mode only. If that case, it is necessary to ensure that plugins are also built in release mode. Otherwise, you can open the solution file for Qt, and recompile Designer in debug mode.

==Running Qt Designer with the correct environment variables==
*On Windows, compile Slicer in the same build mode than Qt. If Qt is in Debug mode, compile Slicer in Debug mode, if it's in Release or Debug&Release mode, compile Slicer in Release mode.
*run Qt Designer via Slicer launcher located in Slicer-build.
{| style="border: 1px solid darkgray;"
!align=left style="border-bottom: 1px solid grey;"|Mac Os X
!align=left style="border-bottom: 1px solid grey;"|Linux
!align=left style="border-bottom: 1px solid grey;"|Windows
|-
|colspan="2"|
$ cd Slicer-build
$ ./Slicer --designer
|
> cd Slicer-build
> .\Slicer.exe --designer
|}
{|
|[[Image:Screenshot-Qt Designer.png|thumb|300px|Qt Desginer loaded with CTKWidgets and qMRMLWidgets]]
|}

==Build Slicer==
* Once you are satisfied with UI, save the file, quit Designer and build Slicer to take the changes into account.
{| style="border: 1px solid darkgray;"
!align=left style="border-bottom: 1px solid grey;"|Mac Os X
!align=left style="border-bottom: 1px solid grey;"|Linux
!align=left style="border-bottom: 1px solid grey;"|Windows
|-
|colspan="2"|<pre>$ make -j4</pre>
| Open the inner solution file ''...Slicer-Superbuild\Slicer-build\Slicer.sln'' and build the solution (F7) or build project <code>qSlicerMY_MODULE_NAMEModuleWidgets</code>
|}
It generates a ''ui_qSlicerMY_MODULE_NAMEModule.h'' file in ''...Slicer-Superbuild/Slicer-buildModules/Loadable/MY_MODULE_NAME/''.

That file is used by ''...Slicer4/Modules/Loadable/MY_MODULE_NAME/qSlicerMY_MODULE_NAMEModuleWidget.cxx''.

Note: The <code>objectName</code>s of each widget in the UI correspond (see the Property editor) to the variable names in C++. From your code, you can access the widgets by their objectName.
* And launch Slicer to see the result
{| style="border: 1px solid darkgray;"
!align=left style="border-bottom: 1px solid grey;"|Mac Os X
!align=left style="border-bottom: 1px solid grey;"|Linux
!align=left style="border-bottom: 1px solid grey;"|Windows
|-
|colspan="2"|<pre>$ ./Slicer</pre>
| <pre>> .\Slicer.exe</pre>
|}

← Older revision		Revision as of 07:30, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	=Using custom widgets in Qt Designer=		=Using custom widgets in Qt Designer=
	==Straight to the point==		==Straight to the point==

← Older revision		Revision as of 16:48, 28 June 2012
Line 73:		Line 73:
	\| <pre>> .\Slicer.exe</pre>		\| <pre>> .\Slicer.exe</pre>
	\|}		\|}
		+	== Frequently Asked Questions ==
		+	* My [http://slicer.org/doc/html/classqMRMLNodeComboBox.html qMRMLNodeComboBox] widget is always disabled (gray) in my module.
		+	To be enabled, qMRMLNodeComboBox needs a MRML scene. You can set a MRML scene to the combobox programmatically or directly from Qt Designer. For the latter, you need to be in [http://doc.qt.nokia.com/{{documentation/{{documentation/version}}/qtversion}}/designer-connection-mode.html Connection mode] and connect the signal [http://slicer.org/doc/html/classqSlicerWidget.html#a9c28318f7810ccce517ea7a1b0051da4 mrmlSceneChanged(vtkMRMLScene)] of the module panel (of type [http://slicer.org/doc/html/classqSlicerWidget.html qSlicerWidget]) with the slot [http://slicer.org/doc/html/classqMRMLNodeComboBox.html#a2249be3ccec4783b592f738f1ef7bea3 setMRMLScene(vtkMRMLScene)].

@@ Line 15: / Line 15: @@
 *the first (not detailed here) is to copy (or symlink) the CTK and MRML plugin libraries into <i>%QT_DIR%/plugins/designer</i>,
 *the second is to set the environment variable <code>QT_PLUGIN_PATH</code> to the directory <i>Slicer-build/bin</i> containing the subdirectory <i>designer</i> with the plugin libraries.<br>
-'''Note:''' Qt requires that the directory containing the designer plugins is named "designer".<br>
 === Windows notes ===
 On Windows, Qt Designer can only load plugins that have been compiled in the same build mode than Qt Designer. For example, if Qt is built in Debug mode, the plugins must also be built in Debug mode to be loaded by Qt Designer.<br>

← Older revision		Revision as of 16:16, 8 June 2012
Line 1:		Line 1:
−	~~Back to [[Documentation/{{documentation/version}}/Developers\|Developers Information]]←~~
−
	=Using custom widgets in Qt Designer=		=Using custom widgets in Qt Designer=
	==Straight to the point==		==Straight to the point==

@@ Line 49: / Line 49: @@
 !align=left style="border-bottom: 1px solid grey;"|Windows
 |-
-|colspan="2"|<pre>$ make -j4</pre>
+|colspan="2"|
 | Open the inner solution file ''...Slicer-Superbuild\Slicer-build\Slicer.sln'' and build the solution (F7) or build project <code>qSlicerMY_MODULE_NAMEModuleWidgets</code>
 |}

@@ Line 8: / Line 8: @@
 ./Slicer --designer
 </pre>
 ==Qt Designer requirements==

@@ Line 35: / Line 35: @@
   > .\Slicer.exe --designer
 |}
 {|
 |[[Image:Screenshot-Qt Designer.png|thumb|300px|Qt Desginer loaded with CTKWidgets and qMRMLWidgets]]
 |}