You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently trying to implement an electron application using threadedClass. When starting a new threaded class I do see a lot of errors thrown. So far I think to have it tracked down to be an issue with the threading context (epectron does not allow worker threads to access electron internals). Do I understand right, that the result of threaded functions is passed on the worker thread?
Please excuse my strange wording. I'm kind of new to node development and my multithreading experience comes from languages that do have better support for multithreading (e.g. C#).
The text was updated successfully, but these errors were encountered:
Unfortunately neither of those PRs change how the library operates. #20 is simply some new tests showing a flaw in the architecture, and #34 is the start of an attempt to make the library be more helpful in informing about the limitations without attempting to improve on them.
As such both PRs do not have a high priority from me to finish as functionally nothing will change other than being clearer when you as a user try to do something which won't work.
As for the original question, I do not have enough understanding of how this library works to answer that
I'm currently trying to implement an electron application using threadedClass. When starting a new threaded class I do see a lot of errors thrown. So far I think to have it tracked down to be an issue with the threading context (epectron does not allow worker threads to access electron internals). Do I understand right, that the result of threaded functions is passed on the worker thread?
Please excuse my strange wording. I'm kind of new to node development and my multithreading experience comes from languages that do have better support for multithreading (e.g. C#).
The text was updated successfully, but these errors were encountered: