kicad-developers team mailing list archive

[Tomasz Wlostowski <tomasz.wlostowski@xxxxxxx>]

On 02.03.2017 15:58, "Torsten Hüter" wrote:
> 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 [..]"
Hi all,

In the meanwhile, I've added support linux/arm and linux/aarch64 for
libcontext, tested on qemu. I'll send a patch later, hope that there'll
be some brave OSX/Windows people to test it ;-)

Cheers,
Tom


> 
> 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
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>