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

Negative delay warning fix for IVVI driver #63

Merged
merged 7 commits into from
Apr 6, 2016

Conversation

AdriaanRol
Copy link
Contributor

As raised in issue #44.
Implements the fix that was allowed by #47.

Tested and am using it now.

@damazter
Copy link
Contributor

looks good 💃

@AdriaanRol
Copy link
Contributor Author

@alexcjohnson
Now that you are back, can we merge this ( @damazter already gave a dancer)?

@alexcjohnson
Copy link
Contributor

Oh sorry - absolutely, 💃

BTW, I could have looked at this a long time ago, just didn't see it. I had to turn down my notification level from github because I'd get too much noise from other repos I'm on (I wish I could set notification levels per repo, have raised that issue with github support)... but I still see stuff immediately if you mention me, so feel free to do that liberally.

@AdriaanRol AdriaanRol merged commit 02771f6 into master Apr 6, 2016
@AdriaanRol AdriaanRol deleted the Adriaan_working_branc branch April 7, 2016 12:11
nataliejpg pushed a commit to nataliejpg/Qcodes that referenced this pull request Aug 30, 2017
* Handle device annotator being run from console with eventloop integration

* store ref to imagedrawer

Otherwise it may close at any time

* Ensure that status is defined

* Support annotating with channel devices

* use forground qt func

* Fix correct function name

* use defined names for fallback
jenshnielsen referenced this pull request in jenshnielsen/Qcodes Sep 21, 2017
* Handle device annotator being run from console with eventloop integration

* store ref to imagedrawer

Otherwise it may close at any time

* Ensure that status is defined

* Support annotating with channel devices

* use forground qt func

* Fix correct function name

* use defined names for fallback
nataliejpg pushed a commit to nataliejpg/Qcodes that referenced this pull request Oct 11, 2017
* Handle device annotator being run from console with eventloop integration

* store ref to imagedrawer

Otherwise it may close at any time

* Ensure that status is defined

* Support annotating with channel devices

* use forground qt func

* Fix correct function name

* use defined names for fallback
jenshnielsen referenced this pull request in jenshnielsen/Qcodes Oct 27, 2017
* Handle device annotator being run from console with eventloop integration

* store ref to imagedrawer

Otherwise it may close at any time

* Ensure that status is defined

* Support annotating with channel devices

* use forground qt func

* Fix correct function name

* use defined names for fallback
jenshnielsen referenced this pull request in jenshnielsen/Qcodes Nov 21, 2017
* Handle device annotator being run from console with eventloop integration

* store ref to imagedrawer

Otherwise it may close at any time

* Ensure that status is defined

* Support annotating with channel devices

* use forground qt func

* Fix correct function name

* use defined names for fallback
jenshnielsen referenced this pull request in jenshnielsen/Qcodes Nov 23, 2017
* Handle device annotator being run from console with eventloop integration

* store ref to imagedrawer

Otherwise it may close at any time

* Ensure that status is defined

* Support annotating with channel devices

* use forground qt func

* Fix correct function name

* use defined names for fallback
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.

3 participants