Is the variable feed rates for gray scale raster lasing still there in LaserWeb3 and gone in LaserWeb4? I want to make sure I understand the situation right.
Alright. So I did understand things right. What is the seperate rasterizer branch about? Is that an experiment zone for merging or something?
Someone had a raster issue with no near white darkening and I believe the person was ising LW3 so it should still be available but nobody seemed to reply to my suggestions for variable feed rate lasing. That is why I was looking into this in the first place.
Dev es6?
src/lib/http://cam-gcode-lasercut.js seems to be where to insert variable feedrate if you do not seperate out feedrate and power from svg and raster into a postprocess step that would take brightness and turn it into power and speed.
Well, I noted it for now. It can be discussed more later. For now, I wonder if I can get my mind to shut up so I can sleep. I do not even feel very tired and it is probably about time for you to go to bed when you are on the other side of the world. I did not get any sleep. Ugh.
Oh. GMT+2. Huh. I guess I had it wrong for a while then.
cam-gcode-lasercut.js only handles laser cutting, not rastering. cam-gcode.js selects between calling cam-gcode-lasercut.js, cam-gcode-mill.js, and lw-rasterizer.
Yet the thing that he mentioned does not seem to confain such a file. :-/
Ah. Not only am I messing up my wording, I looked at the wrong one of two suspect sources. Okay. Why two repos for what seems to be fhe same topic? Any idea?
Okay.