Re: Temporarily yielding SolarMutex to another thread

2019-02-02 Thread Jan-Marek Glogowski
Am 2. Februar 2019 14:49:29 MEZ schrieb Noel Grandin : >Assuming that there is no other way to accomplish this, how could it >work >to allow multiple child widgets to "own" the SolarMutex simultaneously? >We >just need one of those threads to trigger an update to something like a >cache, and one of

Re: Temporarily yielding SolarMutex to another thread

2019-02-02 Thread Noel Grandin
Assuming that there is no other way to accomplish this, how could it work to allow multiple child widgets to "own" the SolarMutex simultaneously? We just need one of those threads to trigger an update to something like a cache, and one of the other threads is likely to crash because of a stale poin

Re: Temporarily yielding SolarMutex to another thread

2019-02-01 Thread Luboš Luňák
On Friday 01 of February 2019, Noel Grandin wrote: > On Fri, 1 Feb 2019 at 17:11, Luboš Luňák wrote: > > - Calc threading - the Interpret() call may spawn several threads to > > compute > > This case smells like this functionality should be using a different mutex > instead of the SolarMutex, then

Re: Temporarily yielding SolarMutex to another thread

2019-02-01 Thread Noel Grandin
On Fri, 1 Feb 2019 at 17:11, Luboš Luňák wrote: > - Calc threading - the Interpret() call may spawn several threads to > compute > This case smells like this functionality should be using a different mutex instead of the SolarMutex, then the main thread could hold some kind of InterpretMutex, an