Skip to content

[Feature Request] Auto-save G-code after generation / API access to generated G-code #685

@MjkOKO1992

Description

@MjkOKO1992

Hello LaserWeb4 community,

I have a question/request regarding the G-code generation functionality. I'm using LaserWeb4 for preparing laser/CNC projects and I'm facing the following issue:

Problem description:
After clicking the"Generate G-code" button in the CAM tab, the G-code is generated and stored in the application's memory, but it is not automatically saved to a file. To save it, I need to:

  1. Click the "Save G-code" button (or use the download icon)
  2. Manually specify the filename and location each time

This becomes cumbersome with repeated generation, especially when I want to automate the process.

What I want to achieve:

· Automatic saving of G-code to a file immediately after generation completes (after reaching 100% on the progress bar)
· Or programmatic access to the generated G-code through an API/webhook/other interface
· Integration with my own program (G-code overlay on camera feed) which needs the freshly generated file

What I've already checked:

· G-code is stored in the Redux store (action GCODE_SET)
· The G-code is fully generated before the save dialog appears
· I've tried hooking into the JavaScript console, but this is a temporary and impractical solution

My questions:

  1. Is there a hidden auto-save option in LaserWeb4?
  2. Does the desktop (Electron) version offer more capabilities than the web version?
  3. Is it possible to pass G-code as a URL parameter or through inter-process communication?
  4. Are there plans to add API/webhook support for automated workflow?

Feature request:

· Add an "Auto-save G-code after generation" option in settings
· Ability to specify save path and filename pattern
· Option to call an external script/command after G-code generation

Thank you in advance for your help and suggestions. LaserWeb4 is a great tool, and this functionality would significantly improve my workflow automation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions