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

Proof of concept gcode comment section skip #67

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

gb0101010101
Copy link
Contributor

Wanted to get feedback on this proof of concept feature to add buttons that skip through gcode file by finding comment lines like "(Some gcode comment)". It adds additional buttons "<(S)" and "(S)>" to the gcode move area (desktop version only for now).

Does this seem worthwhile pursuing?

  • It does work for me using a Fusion360 Malsow Post Processed gcode file.
  • It only matches comments where open bracket is at beginning of line so will ignore inline comments.
  • I also made it ignore "(MSG, *)" which is a gcode display message. (Is this even implemented in Webcontrol?)
  • Are there any others comment formats that should be ignored e.g. "(LOG, log message)"?

Please do not commit this as it is not complete and just proof of concept.

…f control elements, add styles for cleaner display.
…ra closing brackets from JavaScript action calls, Add controls div for styling, Add feather icons, fix button layout, Remove 'Dist to move text' to optimize space, Move 'Def. Home' button.
@davidelang
Copy link

davidelang commented Jan 17, 2020 via email

@madgrizzle
Copy link
Collaborator

Comments don't get stripped anymore when the file is loaded (the only thing that gets stripped are blank lines) but webcontrol does strip them, in real time, while sending them to the controller.

This could be a handy addition.

@madgrizzle
Copy link
Collaborator

I also made it ignore "(MSG, *)" which is a gcode display message. (Is this even implemented in Webcontrol?)

No, that's not implemented (first I've seen of that)

Are there any others comment formats that should be ignored e.g. "(LOG, log message)"?

None of those commands are implemented, so I'd leave it up to you if you want to skip them or not.

But overall, I like it very much. I merged your PR into a 'test' branch I made that had your UI-improvements merged, but the "(S)>" came out on its own line.

image

@gb0101010101
Copy link
Contributor Author

the "(S)>" came out on its own line.
The buttons have a lot of left/right padding. I added temporary "moveButtons" class to the div.row that houses them and reduced it in CSS. Perhaps you missed that in the merge?

@madgrizzle
Copy link
Collaborator

Are you still working on this? I like the functionality of it.

@madgrizzle
Copy link
Collaborator

.. and what's your maslow forum handle so I know.. its hard to keep track of people when github name is different than the forum name.

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

Successfully merging this pull request may close these issues.

3 participants