Add printer-specific post-processing scripts configuration #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the ability to configure post-processing scripts at the printer level, allowing users to define scripts that run automatically for all prints using a specific printer configuration.
Changes Made
1. New Configuration Option
printer_post_processconfiguration option to thePrintConfigclasspost_processto avoid conflicts2. User Interface
3. Enhanced Execution Logic
run_post_process_scripts()to handle both printer-level and print-level scriptsUse Cases
Example Usage
Configure in Printer Settings:
Example Python script:
Backward Compatibility
Files Modified
src/libslic3r/PrintConfig.hpp- Added printer_post_process config optionsrc/libslic3r/PrintConfig.cpp- Configuration definition with tooltipssrc/slic3r/GUI/Tab.cpp- UI integration in printer settingssrc/libslic3r/GCode/PostProcessor.cpp- Enhanced execution logicFixes #1.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.