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

[API] TimeConductor API not mapped to internal time conductor #1333

Closed
larkin opened this issue Nov 24, 2016 · 2 comments
Closed

[API] TimeConductor API not mapped to internal time conductor #1333

larkin opened this issue Nov 24, 2016 · 2 comments
Assignees
@larkin @akhenry
Milestone
Roddenberry

Comments

@larkin
Copy link
Contributor

larkin commented Nov 24, 2016

Attempted to use time conductor api via openmct.conductor. It doesn't seem to be linked to the active instance of the time conductor-- everything returns undefined or errors unceremoniously.

In the environment I'm testing in I have activated platform/features/conductor-v2/compatibility and platform/features/conductor-v2/conductor

May be "not-a-bug", need to investigate further.
@larkin larkin added this to the Roddenberry milestone Nov 24, 2016
@akhenry
Copy link
Contributor

akhenry commented Nov 25, 2016

Yeah I found this when I tried to use it from the new API as well. There is a duplicate TimeConductor object that appeared as part of the new API. I actually fixed this in #1287 (but failed to mention it in the description), so it will be resolved when that's merged.

@larkin
Copy link
Contributor Author

larkin commented Nov 25, 2016

Great! Closed with #1287.

@larkin larkin closed this as completed Nov 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@larkin larkin

@akhenry akhenry

Labels
None yet
Projects
None yet
Milestone
Roddenberry
Development

No branches or pull requests
2 participants
@larkin @akhenry