Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Demo INST commanding screen broken #752
@ryanatball This was implemented due to ticket #673 but I think I've effectively obfuscated the basic use case because now you have to wrap everything in Qt.execute_in_main_thread to do anything. I'd like to basically revert this change and create a new widget called backgroundbutton_widget which spawns the new thread. This way the default use case of simply reading another GUI element "just works" but you can use backgroundbutton_widget to do all kinds of fancy stuff without blocking the GUI. Thoughts?
That sounds fair. Unfortunately we are bound by the GUI on this, having the buttons execute in a thread is a better solution otherwise. I'm guessing a lot more files would need to change to add the execute_in_main_thread calls into the widgets such that the button evaled code wouldn't need to care?