I'm ok with it.
Wait @tcanabrava and @rizzitello to review as well.

I think that need the unit showing in the textbox, like mm, cm, m.

int32_t

@abetts One of the most important things in a 3D printer are:

• 4 Axis control
  • To control X, Y, Z, and E (the extruder, the guy that extrude plastic to create the 3D object)
  • The control need to be able to move with steps from 10cm to 0.01mm. (This values can change from printer to printer).
  • The extruder control should have a extruder multiplier that changes the extrusion quantity from 0.5x to 2x.
• Temperature control
  • This sets the temperature in the extruder and the heated bed. The max values should be set by the user.
• Command mode
  • The user should be able to send machine code to the printer, allowing some personalization.
  • This command code should output data from the printer and show to the user as well, like a normal terminal.

Hello Andres, Thank you for your first mockup.
But I would like to comment some points.

• WIP

In D15224#319169, @rizzitello wrote:

In D15224#319158, @patrickelectric wrote:

If you want to put a scale, we should remove the intern circles and only let one xyz control without 0.1,1,10 buttons, only 1x.

This is a way to allow fractional movement on the pie controller. do u think i should just change the defaults to 0.1 1 10 and drop the scale completely ?

If you want to put a scale, we should remove the intern circles and only let one xyz control without 0.1,1,10 buttons, only 1x.

I DON'T WANT TO BREAK THE BINARY COMPATIBILITY BETWEEN THE PLUGINS !!!!
pls, review with love.

Some corrections/notes:

• Should be able to use in smartphones as well.
• 3D rendering of the gcode and update of the viewer while showing the printing progress.
• View for multiple camera monitoring
• The extruder and extrusion/retract need to handle multiple extruders.
• The extrusion and retract should allow the user to control the length of the filament (not a simple up down arrow).
• Panel for connectivity configuration (connecting to remote service of atcore).
• Show notifications for when:
  • print start
  • print finish
  • Something is wrong (YOUR PRINTER IS IN FIRE !)
    • If possible, showing a picture with the notification, showing the actual state of the printer.
  • Allow specific notifications like: Changing layer and etc.

I'll need to test this patch. Probably in the weekend.

Tested and working on mac

Yes, if someone is forcing a int is because he knows what he is doing (or
not).
In either case, if you are using a int as argument the compiler will not
accept.

Are this patch rebased on master ? It appears to be not.

They are const variables inside the scope.

In D13780#284403, @rizzitello wrote:

Why ? and why only for these two

• plugins: Add missing emit

• testclient: Use mult args QString in arg

I think that everything is ok, but I would prefer others review to see if this PR is suitable. I have my doubts

In D13258#271798, @rizzitello wrote:

In D13258#271797, @patrickelectric wrote:

In D13258#271795, @rizzitello wrote:

Thinking something like..

ttyS0 ? How is that possible ?

idk this is just there with my ryzen machine

In D13258#271795, @rizzitello wrote:

Thinking something like..