Hi Justin, thanks for getting back.
I will try out with the examples you have provided, greatly appreciated for
it. And see how much can I do.
Some questions I have in mind though, if you do not mind answering... It is
a bit off-topic..
Generally when I wrote my ui code, it comes in its own class with the
necesasry initialization and after the `self.connect_signals()` I will be
scripting in the functions/ methods for the signals,
or addiitonal functions that is required.
# UI file
class UIManager(QtGui.QDialog):
def __init__(self, parent=None):
#QtGui.QDialog.__init__(self, parent)
super(UIManager, self).__init__(parent)
self.tool_title = 'UI MANAGER'
self.setWindowTitle(self.tool_title)
self.setModal(False)
self.init_ui()
self.connect_signals()
self.setFixedSize(QtCore.QSize(450, 1000))
def button_signal_action(self):
...
...
# More and coming functions for the signals or any other functions
...
...
def main():
dialog = UIManager()
dialog.show()
return dialog
At times, I will create a script called utils file if there are functions
that are either used in the UI file/ shared across with other scripts for
easy maintenance
1. In such cases, should the signals functions and the ui initialization be
separated into 2 different files?
2. If there are several classes within a script file in which it can make
debugging un-manageable, while I think it will be better to break up these
classes
into separate files, is it wise to do so? If so, what are some of the
procedures to take note of?
--
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/073d1400-a3ad-423e-9463-d7c31c4a3a40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
