Good explanation! I have a case where some other thread updates UI element (text box). In that case, how is the connection made (from some worker thread) and the text data passed (to be shown in the text box widget)? The UI starts the worker thread and the worker thread periodically updates the UI with changing data. Every example I have seen seems to use the type: some_UI_widget.some_action.connect() rather some function in another non-UI thread to connect back to a widget in UI. Also, an example of 'bound signal' (signal bounded to an instance, rather than signals declared as class variables would be appreaciated. Thanks!
These videos are great, Jason, thank you! The one thing that could make them ideal is to include a link to the source code (zip) in the video. I like to go back over the code to follow connections, etc., and it is hard to do when the code scrolls out of view in your video.
I'm new to PySide. Signals and Slots was all new to me. Thank you for a great tutorial!
great explanation thank you
Thank you so much. None explains like you. You are a real teacher!!!
Thank you very much.. best explanation I saw yet!
Thank you for a very interesting and well presented video.
Good explanation!
I have a case where some other thread updates UI element (text box). In that case, how is the connection made (from some worker thread) and the text data passed (to be shown in the text box widget)? The UI starts the worker thread and the worker thread periodically updates the UI with changing data.
Every example I have seen seems to use the type: some_UI_widget.some_action.connect() rather some function in another non-UI thread to connect back to a widget in UI. Also, an example of 'bound signal' (signal bounded to an instance, rather than signals declared as class variables would be appreaciated. Thanks!
Thank you. That was very informative.
Great video. Thank you!
What an amazing video!
These videos are great, Jason, thank you! The one thing that could make them ideal is to include a link to the source code (zip) in the video. I like to go back over the code to follow connections, etc., and it is hard to do when the code scrolls out of view in your video.
I may do something like that in the future.