11 May
2013
11 May
'13
8:35 p.m.
On 22/04/2013 06.30, Vicente J. Botet Escriba wrote:
I don't know your constraints: Why do you need to run the setup on the new created thread? Could it be executed directly on the widget constructor?
I have the same pattern in my framework and I solved it with a simple barrier (however I incour in an extra syncronization not needed, indeed the created thread body has to wait has well that the thread creator reaches the barrier. In my very case the setup *has* to be run by the thread because in my case the setup does: 1) cpu affinity 2) thread priority change Regards Gaetano Mendola