Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed fix for 1352 Mk2, move the loaded instrument to the parent thre... #1557

Merged
merged 1 commit into from
Jan 10, 2015
Merged

Proposed fix for 1352 Mk2, move the loaded instrument to the parent thre... #1557

merged 1 commit into from
Jan 10, 2015

Conversation

curlymorphic
Copy link
Contributor

Proposed fix for #1352 Mk2, move the loaded instrument to the parent thread.

address the issue in #1550.

This moves the loaded instrument back to the parent thread, for thread affinity.

I did try another totally different implementation, using signals, and slot and QueuedConnecton, to process the loading in the event loop, as opposed to immediately, but this still caused the same deadlock.

The issue with my previous pull request #1519, was the the instrument was loaded on a separate thread, and needed to be on the same thread as the parent TrackContainer to be able to use the Qt event loop

@tresf
Copy link
Member

tresf commented Jan 10, 2015

Thanks for following up with this. Merging, since you were the author of #1519.

tresf added a commit that referenced this pull request Jan 10, 2015
Proposed fix for 1352 Mk2, move the loaded instrument to the parent thre...
@tresf tresf merged commit afa55ca into LMMS:master Jan 10, 2015
@curlymorphic curlymorphic deleted the i1352 branch July 5, 2015 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants