Feature: Move head to mouse position.

[t-oster]

See #176.
TODO:

• write a draft code
• Get my pull-request into the LAOS firmware (Do not go to rest after job. LaosLaser/Firmware#10)
• Find a reasonable resolution: using the highest available
• Internationalization (develop...feature-move-head-position#diff-dd385dda36b213a0d089058e49e332cbR115)
• Improve the UI
• Move the code to LibLaserCut for interactive lasercutter-features instead of sending an empty job (add support for jogging, interactive lasercutter controls etc.)

[mgmax]

What is the difference if we don't use the highest possible resolution?
BTW: With 200dpi a pixel is 0,127mm wide and I doubt anyone can see a position difference of 0,1mm, so that would not matter.

[t-oster]

Well the only reason I could think of, would be somebody trying to cut in a very low resolution, which will have a different position after mapping to the grid than the move-head position will be, but that's rather artificial. So I guess just taking the highest resolution makes most sense.

[krekr]

This is awesome! I haven't had the time to check out the version you hacked together, but I will soon.
One thing I'm thinking is: even if you're working with Epilog machines or "stock Laos firmware", you could just send an empty job with only a move-to-position command, right? Or have it only "cut" out a rectangle of the bounding box with the laser power off. I don't know the protocols that well, but this should be possible.

[t-oster]

Hi...as pointed out the problem is, that the lasercutter would move to the desired position, but immediately return to the 'home' position

[peteruithoven]

You could add a ticket to the LAOS issue queue to ask for something like a "gotoRest" boolean in the configuration. This could enable and disable the automatic movement to a rest position. (The rest position is something else then the home position)
http://redmine.laoslaser.org/projects/laos/issues

[t-oster]

I already did this in their Issue list ( LaosLaser/Firmware#10 know they still have an additional redmine though.

[peteruithoven]

Ah I see. I forgot. I think we/they mostly use redmine's issue queue.

[krekr]

Good enough for me ;)

[t-oster]

well... it already sends an empty job, so it should also work with other lasercutters...

[t-oster]

well there will be more features (at least for the LAOS) as soon as the new "direct-execute" format is there, but I will merge this anyways, since it should not break anything.