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

GCode entry screen #15

Open
johnboiles opened this issue Apr 27, 2019 · 5 comments
Open

GCode entry screen #15

johnboiles opened this issue Apr 27, 2019 · 5 comments

Comments

@johnboiles
Copy link
Contributor

I'm thinking about building a GCode entry screen in addition to the existing axes workspace and connection screens. I think the buttons would be something like this:

☰ ======= > x
    G 7 8 9 <  
    M 4 5 6 ⏘
      1 2 3 
      - 0 .

Thoughts or suggestions?

@MitchBradley
Copy link
Collaborator

Cncjs-shopfloor-tablet has a pop up calculator that appears when you touch a numeric field. It could be adapted to be a separate screen like you suggest

@MitchBradley
Copy link
Collaborator

More thoughts: about the second time you use it you will wish for full MDI which means you will need X Y Z F and maybe A S P. But you will run out of LCD real estate pretty fast so how about this: there is an MDI screen with those letters and when you enter a letter it switches to the number entry screen (or calculator). When you finish a number it goes back to the MDI screen where you can enter the next letter - then to the number screen again, etc

@MitchBradley
Copy link
Collaborator

Oh, and having at least two saved MDIs is super handy so the top level MDI screen might have multiple slots

@johnboiles
Copy link
Contributor Author

I think you have 6x5 spaces for buttons maybe 6x6 even. What about

☰ ===== > x
G X 7 8 9 <  
M Y 4 5 6 ⏘
A Z 1 2 3 -
S F P 0 .

Where the ===== would show the GCode, < is a backspace icon, > is run, x means clear all, means space

@johnboiles
Copy link
Contributor Author

Your idea about switching / popups is good, just adds some complexity. It could even be context aware and only show/enable buttons that would be valid next inputs based on what was written so far.

Though thinking I want to start simple so that I have a better shot of finding time for this.

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

2 participants