I am getting confused. So I need to back up a bit. It all relates to being able to launch a pyside_dynamic ui in maya.
I have been asked to drop this pyside_dynamic2.py file (see attached) into my maya scripts dir. When I try to import it I get this error. import pyside_dynamic2 # Error: No module named PySide.QtCore # Traceback (most recent call last): # File "<maya console>", line 1, in <module> # File "C:/Users/justin/Documents/maya/2017/scripts\pyside_dynamic2.py", line 42, in <module> # from PySide.QtCore import Slot, QMetaObject # ImportError: No module named PySide.QtCore # Do I need to edit this script or is it redundant now with maya2017 ? -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/12512750-bd01-4dfb-b8e8-0abdefd955c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
#!/usr/bin/python2 # -*- coding: utf-8 -*- # Copyright (c) 2011 Sebastian Wiesner <[email protected]> # Modifications by Charl Botha <[email protected]> # * customWidgets support (registerCustomWidget() causes segfault in # pyside 1.1.2 on Ubuntu 12.04 x86_64) # * workingDirectory support in loadUi # found this here: # https://github.com/lunaryorn/snippets/blob/master/qt4/designer/pyside_dynamic.py # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING # FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER # DEALINGS IN THE SOFTWARE. """ How to load a user interface dynamically with PySide. .. moduleauthor:: Sebastian Wiesner <[email protected]> """ from __future__ import (print_function, division, unicode_literals, absolute_import) import os import sys from PySide.QtCore import Slot, QMetaObject from PySide.QtUiTools import QUiLoader from PySide.QtGui import QApplication, QMainWindow, QMessageBox SCRIPT_DIRECTORY = os.path.dirname(os.path.abspath(__file__)) class UiLoader(QUiLoader): """ Subclass :class:`~PySide.QtUiTools.QUiLoader` to create the user interface in a base instance. Unlike :class:`~PySide.QtUiTools.QUiLoader` itself this class does not create a new instance of the top-level widget, but creates the user interface in an existing instance of the top-level class. This mimics the behaviour of :func:`PyQt4.uic.loadUi`. """ def __init__(self, baseinstance, customWidgets=None): """ Create a loader for the given ``baseinstance``. The user interface is created in ``baseinstance``, which must be an instance of the top-level class in the user interface to load, or a subclass thereof. ``customWidgets`` is a dictionary mapping from class name to class object for widgets that you've promoted in the Qt Designer interface. Usually, this should be done by calling registerCustomWidget on the QUiLoader, but with PySide 1.1.2 on Ubuntu 12.04 x86_64 this causes a segfault. ``parent`` is the parent object of this loader. """ QUiLoader.__init__(self, baseinstance) self.baseinstance = baseinstance self.customWidgets = customWidgets def createWidget(self, class_name, parent=None, name=''): """ Function that is called for each widget defined in ui file, overridden here to populate baseinstance instead. """ if parent is None and self.baseinstance: # supposed to create the top-level widget, return the base instance # instead return self.baseinstance else: if class_name in self.availableWidgets(): # create a new widget for child widgets widget = QUiLoader.createWidget(self, class_name, parent, name) else: # if not in the list of availableWidgets, must be a custom widget # this will raise KeyError if the user has not supplied the # relevant class_name in the dictionary, or TypeError, if # customWidgets is None try: widget = self.customWidgets[class_name](parent) except (TypeError, KeyError) as e: raise Exception('No custom widget ' + class_name + ' found in customWidgets param of UiLoader __init__.') if self.baseinstance: # set an attribute for the new child widget on the base # instance, just like PyQt4.uic.loadUi does. setattr(self.baseinstance, name, widget) # this outputs the various widget names, e.g. # sampleGraphicsView, dockWidget, samplesTableView etc. #print(name) return widget def loadUi(uifile, baseinstance=None, customWidgets=None, workingDirectory=None): """ Dynamically load a user interface from the given ``uifile``. ``uifile`` is a string containing a file name of the UI file to load. If ``baseinstance`` is ``None``, the a new instance of the top-level widget will be created. Otherwise, the user interface is created within the given ``baseinstance``. In this case ``baseinstance`` must be an instance of the top-level widget class in the UI file to load, or a subclass thereof. In other words, if you've created a ``QMainWindow`` interface in the designer, ``baseinstance`` must be a ``QMainWindow`` or a subclass thereof, too. You cannot load a ``QMainWindow`` UI file with a plain :class:`~PySide.QtGui.QWidget` as ``baseinstance``. ``customWidgets`` is a dictionary mapping from class name to class object for widgets that you've promoted in the Qt Designer interface. Usually, this should be done by calling registerCustomWidget on the QUiLoader, but with PySide 1.1.2 on Ubuntu 12.04 x86_64 this causes a segfault. :method:`~PySide.QtCore.QMetaObject.connectSlotsByName()` is called on the created user interface, so you can implemented your slots according to its conventions in your widget class. Return ``baseinstance``, if ``baseinstance`` is not ``None``. Otherwise return the newly created instance of the user interface. """ loader = UiLoader(baseinstance, customWidgets) if workingDirectory is not None: loader.setWorkingDirectory(workingDirectory) widget = loader.load(uifile) QMetaObject.connectSlotsByName(widget) return widget class MainWindow(QMainWindow): def __init__(self, parent=None): QMainWindow.__init__(self, parent) loadUi(os.path.join(SCRIPT_DIRECTORY, 'mainwindow.ui'), self) @Slot(bool) def on_clickMe_clicked(self, is_checked): if is_checked: message = self.trUtf8(b'I am checked now.') else: message = self.trUtf8(b'I am unchecked now.') QMessageBox.information(self, self.trUtf8(b'You clicked me'), message) @Slot() def on_actionHello_triggered(self): QMessageBox.information(self, self.trUtf8(b'Hello world'), self.trUtf8(b'Greetings to the world.')) def main(): app = QApplication(sys.argv) window = MainWindow() window.show() app.exec_() if __name__ == '__main__': main()
