Allow outputs to have different message formats

[Yoooi0]

Rework "Device" settings tab to only define MFP internal axes (no value precision).

Add ability to define message format with MFP axis name, target value, move duration variables. How to make the computation fast? Expressions? Or just CompositeFormat but cant have any logic. Allow switching between fast or slow types? StepCount for rounding MFP axis value to output value (kinda like precision)? Allow message format per MFP axis or one for all. Add default TCode formats.

In outputs allow selecting output format, default to TCode. What to do with update context?

Also resolves #147 since you could add multiple MFP axes that output same TCode axis message.

Outputs that can support this:

• TCP
• UDP
• Serial
• WebSocket
• NamedPipes
• MQTT #211

[eglische]

just saying; if you need mqtt as user, that means you go basically running something like node-red. so you could just do it via websocket, and bridge it over to mqtt if needed.

for yooooi: if you really go the mqtt output way - i would consider to do also the shortcuts via mqtt and websockets... i wont be "mad" if you outdate my fork by this move if that is any consideration ;)

[Yoooi0]

Yea unfortunately I have a particular way of segmenting code, a lot of features could be easily implemented but I don't like when code accesses too much or does not belong somewhere.

I think shortcuts/actions etc. should be in some kind of websocket remote control api. Probably can just put it in a tab in settings. Device axis value input should ideally be done after #121, supporting TCP/UDP/websocket/serial/mqtt/pipe. Basically mirroring the current outputs. Alternatively it could be put into the remote control api if #121 is not implemented. And mqtt output can be easily added once this is implemented.