You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2020. It is now read-only.
open a project with a previously-saved uniquely named control schema (e.g. "robot schema")
close that project
open a different project with a previously-saved uniquely named control schema (e.g. "monster schema")
choose Control Schema -> Open command (or, similarly, Control Schema -> Save)
Note that schemas from both projects are listed, even though you closed the other project.
This is unexpected. Indeed, if you close the CDK entirely, relaunch it, and open just the second project, only one schema is listed on open/save.
If there's some intentional plan to let me open schemas from other projects this way, then I love that idea, but it needs work. In fact, I discovered this bug while copying/pasting a schema from another project. :) But as things stand now, I expect this is a bug, right?
I didn't try taking this any farther (e.g. opening the cross-project schema or saving to the other project's schema), 'cause I didn't want to mess up my projects. Bad things might happen there, too.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Note that schemas from both projects are listed, even though you closed the other project.
This is unexpected. Indeed, if you close the CDK entirely, relaunch it, and open just the second project, only one schema is listed on open/save.
If there's some intentional plan to let me open schemas from other projects this way, then I love that idea, but it needs work. In fact, I discovered this bug while copying/pasting a schema from another project. :) But as things stand now, I expect this is a bug, right?
I didn't try taking this any farther (e.g. opening the cross-project schema or saving to the other project's schema), 'cause I didn't want to mess up my projects. Bad things might happen there, too.
The text was updated successfully, but these errors were encountered: