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

MachineControl Package naming #10

Open
DavidWLoupe opened this issue Feb 21, 2023 · 0 comments
Open

MachineControl Package naming #10

DavidWLoupe opened this issue Feb 21, 2023 · 0 comments

Comments

@DavidWLoupe
Copy link
Member

The documentation in LoupeDocs (Libraries > Piper > Usage) and in piper source files (e.g. MachineControl.var header) refer to a package named "MachineControl", yet no such named package exists in the repo.

If a user wanted to "Add Existing Package", they would need to add the repo folder, then rename to MachineControl.

Is "MachineControl" an old name that should be replaced with "Piper"? Or is that what we simply always call the package with Piper stuff in it? Either way, there is some inconsistency here that should be straightened out, I believe.

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

No branches or pull requests

1 participant