• rebase

• rebase

• Rebase

• fix wrong emit

• Patricks Suggestion

• Cleaner logic

I think it looks better slightly off the edge of the item and I agree that if its on the item its looks much better with the shaded bar under it. To improve the contrast we could make the button our highlight color when hovered.

• Add examples of regex captures

• Remove added new line and un needed include

• move to new diff

• fix failed Test

• use std::shared_ptr for bed Deform , more examples , capture by name in the regex

• remove extra include

+1

• Add tests

• Use QVariantList and set Q_Property for QML export

• Better explain regex

• Better examples

• Rebase

• Rebase

• rebase

• rebase

• rebase

• documents update

• set then emit

• Missing Const Ref (Thanks Tomaz !)

In T9542#174432, @ngraham wrote:

Thanks for the comments. This is designed not only for embedded but also desktop use. A 3D printer app is one of those cases where I'm not sure a more complicated interface on the desktop makes sense. The workflow and capabilities are basically the same in both cases.

• The last time I had a print farm set up for commercial purposes (granted, this was a few years ago) I personally never had problems with serial ports changing. What is the sanest technical way to handle multiple 3D printers from your perspective?

In that case we would expect them to change. When they can change is for users who use several printers with the same tty controller that do not always have them all atttached. (or any other serial tty device.)

• Does Atelier support exporting gcode to SD cards for printers that have SD card slots? If not, can it?

There is a patch for this but its VERY VERY Slow about 1Kb/s (again serial devices..) D14136

• Does Atelier support connecting via wifi to printers that support it? If not, can it?

Currently no only because I don't have a machine that connects to anything but usb.

• Another question: how is an integrated build camera configured? Is it connected to the printer itself, connected directly to the host and seen as a camera, available via a web URL, or something else? Or any combination of those? Etc.

Can't answer that since none of mine came with a camera installed. Cameras can be any camera. currently we are able to connect to local devices in our camera viewer (idk that anyone has tested an ip camera there).

The basic issue with the auto detect idea is that 3d printers restart when you try to connect to them. If you have more then one and one is printing trying to probe devices can be problematic. The other issue with hard coding a device is the device name can change since its just a serial device and ttyAMC/ ttyUSB devices are common and number will changed based on the order they are plugged in.

I like the general workflow here. This can work nicely for an embedded interface .

Loading STL's with qt3d for the preview seams trivial (with assimp): http://amin-ahmadi.com/2018/01/28/viewing-3d-models-using-qt/

We have plans for slicer plugin support. Just never made a task for it. So I've done that now T10396

• update base

• rebase

• Fix base

• Add return for GCode::toCommand for G29
• Create bedDefrom Object

• replace accidently removed line

• Rebase
• Add missing @param

• Rebase

Seams to function correctly.

• rebase

• correct base