The Wayback Machine - https://web.archive.org/web/20201126114046/https://github.com/OctoPrint/OctoPrint/issues/1153
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

[Request] System command type in Controls structure #1153

Open
NateBowen opened this issue Dec 21, 2015 · 0 comments
Open

[Request] System command type in Controls structure #1153

NateBowen opened this issue Dec 21, 2015 · 0 comments

Comments

@NateBowen
Copy link

@NateBowen NateBowen commented Dec 21, 2015

Related to closed case #1095. I believe it's worthy of another look.

Currently, to create custom system commands a user must use the Event or System structures of config.yaml.

In my specific case, I would like to send a parameter to the system for use with RPi-gpio applications. This would be most intuitively accomplished through the controls structure with a slider or value-entry field.

In the Events structure, the command type is configurable between system and printer/g-code types.
Rather than use a Controls command to send a "dummy" printer command (M300 or other) to trigger an event to send a system command, adding the "type" switch to the Controls structure would allow the script to be sent directly from the Controls command without limiting the user to the predefined Event list or the static nature of the Systems tab.

controls:
..-.children:
....name: xyz
....width: '2'
....type: system <-------------------------------------- new option
....command: gpio abcParameter
....input:
....-.default: 10
......name: abcParameter
......parameter: abcParameter

@GitIssueBot GitIssueBot added the request label Dec 21, 2015
@foosel foosel added this to the Plugins milestone Feb 24, 2016
@foosel foosel added the plugin idea label Mar 10, 2016
@foosel foosel removed this from the Plugins milestone Jun 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.