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.

Sign up for GitHub

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

Jump to bottom

get_trace locks out trace1, returns in remote mode #408

Open
mgiustina opened this issue Feb 2, 2017 · 0 comments
Open

get_trace locks out trace1, returns in remote mode #408

mgiustina opened this issue Feb 2, 2017 · 0 comments

Comments

@mgiustina
Copy link
Contributor

After using get_trace, the PNA is left in a state that is tricky to use locally/manually.

  1. Suppose get_trace has been used to get a signal that the PNA identifies as trace2. Afterward, it is no longer possible to manually activate trace1; one must manually delete trace1 (even if it wasn't in use before) and then manually activate it again.

  2. After calling get_trace in the PNA server, the PNA is left in remote mode. This is not critical, but it would be nice to save the user the regular button-pressing needed to switch back to local mode.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mgiustina