3D-printed book turns its own G-code into raised lettering(designboom.com) |
3D-printed book turns its own G-code into raised lettering(designboom.com) |
https://reprap.org/wiki/G-code#M98:_Call_Macro.2FSubprogram
but Fanuc and other dialects allow M97 to call a subroutine chained to the end of a program.
Because these folks always want to do the least legal thing allowed by law.
Rant: That type of slider-switch is an inferior usurper of the classic tickbox, that rode in on a wave of touch-screen-ification. Oh, it can be done well, sometimes, but it's just far too easy to do it badly.
In this case (useless colors, not other labels) I think the implicit rule/clue is "Move the dot-nub towards what you want." Therefore moving right is indicating you like the "I'm gonna do X to you" text-line, and moving left indicates you don't.
> It feels intentionally misleading.
The dark-pattern behind that "Accept All" button is worse:
1. It abuses color and positioning rules make it look like the button you pick to continue with what the screen already shows.
2. Its text-phrasing exploits the ambiguity between "Enable All" versus "Continue with your choices."
3. When it activates, it does so in a hidden manner. You don't see all the sliders moving from left to right, and you have no chance to confirm that it's what you wanted.
The fact that quines exist means that it must be possible to print a fully self-describing book of this sort, though it's possible that you'd require a more expressive language.
If you had a part of a machine that could save state (say.. turning on a coolant pump..) I wonder how much more of a turing machine you could wrastle into it.
(or you could just cheat and use one of the hundreds of gcode variants that have computational stuff stapled into them like the Fanuc equivalents, but that's sorta dishonest for the exercise)
Grbl, which many of the 3D printer firmwares are based on, does not (and no variables, or loops, or branching).
So suppose I attached an extruder to a Haas mill or something...