VRET pyQt - Revision history

Niels: /* Arguments in callback functions */

2010-01-04T09:34:28Z

‎Arguments in callback functions

2009-12-15T11:39:14Z

‎Arguments in callback functions

2009-12-15T11:37:22Z

‎Links

2009-12-14T09:06:32Z

‎Designer

2009-12-11T13:35:00Z

‎Designer

2009-12-11T13:34:35Z

‎Designer

2009-12-11T13:32:35Z

‎Designer

2009-12-11T13:32:16Z

‎Designer

2009-12-11T13:31:48Z

‎Designer

2009-12-11T13:31:10Z

‎Designer

@@ Line 25: / Line 25: @@
 I think that the Qt Designer intends you to create these callbacks using their editor too.
 Check [http://qt.nokia.com/doc/4.6/designer-connection-mode.html tutorial] how to do this as this is quite un-intuitive involving selecting a connection mode and dragging icons to other icons.
 === Designer ===

← Older revision		Revision as of 11:39, 15 December 2009
Line 20:		Line 20:

	self.connect(self.buttonObject, QtCore.SIGNAL('clicked()'),self.createCallBackFunction("argument"))		self.connect(self.buttonObject, QtCore.SIGNAL('clicked()'),self.createCallBackFunction("argument"))
		+
		+	--
		+
		+	I think that the Qt Designer intends you to create these callbacks using their editor too.
		+	Check [http://qt.nokia.com/doc/4.6/designer-connection-mode.html tutorial] how to do this as this is quite un-intuitive involving selecting a connection mode and dragging icons to other icons.

	=== Designer ===		=== Designer ===

← Older revision		Revision as of 11:37, 15 December 2009
Line 76:		Line 76:

	*[http://www.riverbankcomputing.co.uk/software/pyqt/download pyQt]		*[http://www.riverbankcomputing.co.uk/software/pyqt/download pyQt]
		+	*[http://qt.nokia.com/doc/4.6/designer-connection-mode.html making connections between events(buttonsclicks etc) and code]

@@ Line 51: / Line 51: @@
 ''' Ui to Py '''
-:PyQt comes with a little .bat file named pyuic4.bat that can convert your Ui file into an Py file. The command line for this is ''''pyuic4.bat widget.ui > widget.py''''
+:PyQt comes with a little .bat file named pyuic4.bat (without .bat on *nix; the executable is in PyQt/pyuic/) that can convert your Ui file into an Py file. The command line for this is ''''pyuic4.bat widget.ui > widget.py''''
 ''' Using the generated .py file '''

@@ Line 67: / Line 67: @@
 '''List widgets'''
-With list widgets you need to be carefull to drag the correct one on your workspace. There are Model-Based and Item-Based list widgets the Item-Based ones are the ones you want to use.
+:With list widgets you need to be carefull to drag the correct one on your workspace. There are Model-Based and Item-Based list widgets the Item-Based ones are the ones you want to use.
 [[Image:ListWidgets.jpg]]

← Older revision		Revision as of 13:34, 11 December 2009
Line 67:		Line 67:

	'''List widgets'''		'''List widgets'''
		+	With list widgets you need to be carefull to drag the correct one on your workspace. There are Model-Based and Item-Based list widgets the Item-Based ones are the ones you want to use.
	[[Image:ListWidgets.jpg]]		[[Image:ListWidgets.jpg]]

@@ Line 40: / Line 40: @@
 ''' Layout options '''
 [[Image:LayoutOptions.jpg]]
 ''' Naming conventions '''

@@ Line 30: / Line 30: @@
 :The first step on your empty widget is to put a layout on it by dragging and dropping it from the left menu onto the widget. After doing this you have to fix the layout onto that widget by selecting the widget in the right menu and right clicking it and select Layout> from the pop up menu. In this sub menu you select the kind of layout you put onto the widget and by doing this the layout box will fill the complete widget (except for some borders). After this step you can drag and drop any layout or widget from the left menu onto the widget and it will be placed and sized automatically.
-[[Image:LayoutOptions.jpg]]
 [[Image:LayoutSet.jpg]]
@@ Line 40: / Line 40: @@
 ''' Layout options '''
 :Every layout has it's own options for spacing and margings these can be found also in the right menu when you have the layout or a widget with layout selected.

@@ Line 43: / Line 43: @@
 ''' Naming conventions '''
-[[Image:WidgetNaming.jpg]]
 :Like every Gui editor Designer names it's widget by just nummering them this isn't useful when you want to work with these widgets later on. The way you work with the generated .py files a nice convention to stick with is to name every widget as a coombination of it's function and type and starting every word with a capital letter. so a dropbox on a widget to select an scenario will be 'ScenarioBox'. Starting with a capital letter will make sure you can make a destinction between your own variables in your code and Designer generated objects in your ui.
 :Naming your main widget every widget you create starts with a base (the main widget) you should name this widget the same as the final name you want to use for that class in your code. so a widget for scenario selection named ScenarioSelectionWidget.py should be named in the designer as ScenarioSelectionWidget and saved as Ui_ScenarioSelectionWidget.ui
 ''' Ui to Py '''