secondary thread accessing gui functions

[wxJack]

Hi !
I know that " it is strongly recommended that no secondary threads call GUI functions " .
I think it is mandatory for the writing operation, but what about the reading ones?
Can I let a secondary thread t2 access to a wxListCtrl (whose pointer is passed inside the ctr) so t2 can read some values?
thanks to all !

[T-Rex]

Since reading from wxListCtrl means also usage of GUI-related functionality, it's also not recommended because you may get into race conditions while accessing the UI control from both threads (UI and worker). If you want to send some data to the worker thread, you could probably use wxMessageQueue.
You robably could use a virtual wxListCtrl and access the `model` class for this list control from the thread directly with wxCriticalSectionLocker or wxMutexLocker (depending on your needs), but this may cause delays in your UI's responses if processing time for the data is too long.

[doublemax]

Warning: Enter at your own risk.

Try wrapping the code in wxMutexGuiEnter() / wxMutexGuiLeave().
https://docs.wxwidgets.org/trunk/group_ ... 8ea7ced5b5

You still need to make sure that e.g. you create a deep copy of any wxString you get from the control.

There is still no guarantee that this will work all the time. It also depends on the platform. Windows seems to be more forgiving, while GTK crashes more easily when accessing GUI elements from a secondary thread.