Closed janslow closed 9 years ago
It appears that something goes wrong in Swift or QLabKit when a second cue is created whilst the first is still updating attributes. It seemed to not receive the callback of the second create request, so just stopped.
Marked as won't fix until I have added better multi-threading/async support.
After a cue is created, it should be fine to start the next cue whilst waiting for the attributes (such as name, number and prewait) to be set.
This will speed up the process of appending to the cue list.