anycodings_user-interface drawbacks, pitfalls, praises, etc.) will be anycodings_user-interface appreciated. tResultsWidget(self.results_object)Īny commentary on this approach (e.g. #update results widget for selected thread Self.results_object = self.processing_threads.getResults() #update results_object for thread with results tProgressBar(self.progress_object)ĭef updateResultsObject(self, thread_name): Self.progress_object = self.processing_threads.progress (p_thread, QtCore.SIGNAL('resultsReady(str)'), self.updateResultsObject(thread_name))ĭef updateProgressObject(self, thread_name): (p_thread, QtCore.SIGNAL('progressUpdated(str)'), self.updateProgressObject(thread_name)) #connect thread signals to GuiApp functions ''' this is tivial for shortness sake ''' Self.emit(QtCore.SIGNAL('resultsReady(str)'), self.getName()) Self.emit(QtCore.SIGNAL('progressUpdated(str)'), self.getName()) #emit signal only if progress has changed _pyqtSignals_ = ( 'progressUpdated(str)',

# to read this to answer the question(s).Ĭlass ProcessingThread(threading.Thread, QtCore.QObject):

#NOTE: this is example code for my idea, you do not have anycodings_user-interface Also signal when finished processing so anycodings_user-interface results can be displayed. My Idea: Have the threads emit a QtSignal anycodings_user-interface when the progress is updated that triggers anycodings_user-interface some function that updates the progress bar.

Generally, what are the best practices for.

Qt update gui from worker thread