kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #28403
Re: [PATCH] Fix MacOS coroutine segfault
Chris:
>> With a proper implementation this should be indistinguishable from
>> coroutines, including to wx.
This is your opinion not mine, I'm not sure. Again, read the paragraph about secondary threads:
http://docs.wxwidgets.org/3.1/overview_thread.html
"[..] under Win32 a thread can only access GDI objects such as pens, brushes, device contexts created by itself and not by the other threads [..]"
One of the reasons why they strongly recommend "no secondary threads call GUI functions".
--
However, if you can ensure that the coroutines never call GUI functions, threads should be a nice alternative. I remember Orson has written, that this should be possible. Maybe he can answer the question if this restriction is still acceptable. Then I could rescue my implementation from my backups.
Thanks,
Torsten
Follow ups
References
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Wayne Stambaugh, 2017-03-01
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Tomasz Wlostowski, 2017-03-01
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Chris Pavlina, 2017-03-01
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Tomasz Wlostowski, 2017-03-01
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Chris Pavlina, 2017-03-01
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Wayne Stambaugh, 2017-03-01
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Chris Pavlina, 2017-03-01
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Wayne Stambaugh, 2017-03-01
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Chris Pavlina, 2017-03-01
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Torsten Hüter, 2017-03-02
-
Re: [PATCH] Fix MacOS coroutine segfault
From: Chris Pavlina, 2017-03-02