Hi Thomas, thanks for your reply. On 12/05/2017 04:02 PM, Thomas Heller wrote: > Am 05.12.2017 2:13 nachm. schrieb "Andreas Buhr" <[email protected] > <mailto:[email protected]>>:
[snip] > This principle is ignored in the example: In the example [1], an HPX > thread calls widget::add_label which in turn calls QListWidget::addItem. > I think this should not happen, even when protected with a mutex-lock. > > I modified the code to be correct in my understanding: The widget has > now two threadsafe interface functions: threadsafe_add_label and > threadsafe_run_finished, both of which do not interact with GUI objects. > They might be called from any thread. They in turn schedule the > execution of corresponding functions within the GUI thread. > > Would you agree? I am not a GUI expert, so I'm not sure about my > solution. > I created a pull request [2]. Feel free to accept or reject... > > > You are most certainly correct. Thanks for catching this. Did you run > into any problems with what we have so far? No, I haven't seen any problems with the example. However, I am looking for the right design for a larger application, so I'd like to get it right. best, Andreas _______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
