If "T(\d*)" was "T(\n*)" it would search for newlines. There isn't
any such \d escape character.
It should be "T(\\d*)" or r"T(\d*)" going with the latter, to be
easier to read and be consistent with other Cura usage.
Start python with -Wd or for python 3.12 will raise a SyntaxWarning.
This is an extensive re-do of the script.
# Added an 'Enable' setting
# Added support for multi-line insertions (comma delimited)
# Added insertions in a range of layers or a single insertion at a layer. Numbers are consistent with the Cura Preview (base1)
# Added frequency of Insertion (once only, every layer, every 2nd, 3rd, 5th, 10th, 25th, 50th, 100th)
# Added support for 'One at a Time' print sequence
An update to the script.
- Added insertion frequency
- Added support for relative extrusion
- Retract is now a boolean and the settings come from Cura. There won't be a retraction if there is already a retraction.
Add pause count notification
Update DisplayInfoOnLCD.py
Moved some line insertions to accommodate newer Creality firmware.
Change DisplayFIlename and DIsplayProgress
Add messages to use DIsplay Info and add exit code.
Update DisplayInfoOnLCD.py
Some changes
Get the current print time estimate, adjust it by the Fudge Factor, and add it to the current time +10 minutes (to actually start the print.)
Update DisplayInfoOnLCD.py
Change message format for Finish Time Estimate.
Added Gradual Accel Change.
Update LimitXYAccelJerk.py
Round the Accel numbers to nearest "50".
Create LimitXYAccelJerk.py
New post processor to limit the X and or Y accel and jerk for bed-slinger printers.
Update LimitXYAccelJerk.py
Removed debug code.
Update LimitXYAccelJerk.py
Remove debug code
Update LimitXYAccelJerk.py
Bug Fix
Remove code that added the PP name to the gcode.
Create DisplayInfoOnLCD.py
This post processor combines DisplayLayerAndFilename with DisplayProgress. Those two post processors would be obsolete.
Some printers accept commands like TIMELAPSE_TAKE_FRAME or whatever, after all. Make it explciti that a line should start with T<number> in order to qualify.
Should fix#15729
Users could still set the option first, _then_ switch to Griffin, giving the same problems before the default was switched to false (since the setting is disabled for Griffin flavour anyway).
part of CURA-10451
Hold-stepper-motor (and maybe beep) options, newly introduced previously, _and on by default_ (even though it was clear they where not meant for Griffin flavour GCode -- because at least the hold-motor option was not even visible for Griffin) where causing UltiMaker printers with prints that had the pause-at-height script enabled to fail.
should fix internal ticket CURA-10451
