HotLoop Flow 2.12.0 release notes
HotLoop Flow 2.12.0 finishes the FlowLab panel and the canvas: the knob, the spin entry, the LED, the array and the record are real controls now, a sub-diagram opens in place on the canvas instead of being a second tab to chase, and every instrument’s writes are off until somebody turns them on. It also fixes a control that could not be set before the first run, and it carries the new license. Read “What changed” before you upgrade if a diagram of yours drives an instrument.
What’s new
Section titled “What’s new”- Panel controls, finished. The knob is a dial that sweeps 270 degrees: drag round it with a finger or a mouse, press on it to put it there, or use the arrow keys (one step), Page Up and Page Down (ten steps), Home and End, and it writes when you let go. The spin look is a typed number with minus and plus buttons that step by
stepand stop at the range. The LED look on a switch is an LED you press. An array control is a list of numbers, switches or text that the operator adds to and removes from, held byelem,min,maxandmaxlen. A record control is one input per field offields(rate:number, on:bool, note:string), and the diagram reads an object with every field in it. The server holds each one to its kind and range, whatever you set it with, and says which item or field is wrong. Every control’s touch target on the panel is at least 44 pixels each way and the page does not scroll sideways at 390 pixels wide. - Sub-diagrams open in place. A sub-diagram node has a small box at its corner, and the diagram bar has Open in place for the selected one. The node is drawn open where it was: a frame with its connector named on the left and right edges, and inside it the nodes and wires of its body. They are the body’s own nodes, so moving one, double-clicking it for its properties, wiring two, deleting one or drawing a marquee over some is editing the body, as undoable steps, and a deploy saves it. Closing it puts the node back. Open sub-diagrams can hold open sub-diagrams, three deep, and a body that leads back to one that is already open is drawn closed so a diagram that contains itself cannot loop the editor. Which are open is how you are looking at the diagram: it is not in the flow file, so a deploy sends what it sent before.
- The instrument write switch. Reading an instrument changes nothing and is always open. Writing one can, so every instrument starts with its writes off, and a write from a diagram is refused until someone with the
instrument.writepermission turns that instrument’s writes on.dia-serial-writeis always a write.dia-instr-queryis a read when every SCPI statement in it ends in?and a write otherwise, and a command wired in counts as one that may write. The instrument is its address (tcp://host:portorserial:///dev/ttyUSB0), so one instrument opened two ways is one switch. A refusal is an error on the node’s error wire (code 5007) and the instrument never hears the command.PUT /instruments/writeswith{"instrument": "tcp://10.0.0.5:5025", "allowed": true, "note": "bench 2"}turns one on,GET /instrumentslists them, and the switches live ininstrument-writes.jsonin the data directory. Every switch change is audited asinstrument.switch, every write asinstrument.write, every refusal asinstrument.refused. Deploy lists the instruments a diagram would write to in the diagram bar’s notes.
What changed
Section titled “What changed”- A diagram that drives an instrument stops until you turn that instrument on. On 2.11.x the raw serial and instrument nodes wrote to anything. On 2.12.0 the first write is refused with code 5007 until an admin (or anyone holding
instrument.write) turns that instrument’s writes on. A diagram that only reads is untouched. This is deliberate, the 2.11.0 notes said it was coming, and it is the change in this release that can stop a running diagram. - The knob and LED looks draw what they are named. A number control with the knob look and a range used to draw a typed box, and now draws the dial. A switch with the LED look used to draw a checkbox, and now draws the LED button. A knob with no smallest and largest value still draws a typed entry, and deploy now says so in the diagram’s notes. The slider is unchanged.
- A control can be set before the first run. The panel used to learn its controls only when a run began, so setting one first was refused with “is not a control on this panel”. It learns them from the deployed diagram now, and a stored value that no longer fits a control that a deploy changed goes back to the control’s starting value.
- The canvas. A marquee drawn on a canvas that had been fitted could start somewhere other than where the pointer went, when the content was taller than the canvas, and that is fixed. On a screen narrower than 820 pixels the FlowLab bar used to wrap onto many rows and sit on top of every node. There it takes its own room now. Wider screens are drawn as before.
- The license.
LICENSE,NOTICEand the image’s license label moved from the Business Source License 1.1 to the EmberNet Source License 1.0 (LicenseRef-EmberNet-Source-1.0). They ship inside the image in/usr/share/doc/hotloop-flow. Versions published before this keep the terms they were published under. ReadLICENSEin this release before you rely on it. - Nothing else behaves differently from 2.11.1.
New settings
Section titled “New settings”None in the config file or the environment. A dia-control takes the kinds array and record, the look spin, and the properties elem, maxlen and fields. The permission instrument.write and the file instrument-writes.json in the data directory are the instrument switch. Opening a sub-diagram in place has no setting.
Upgrade
Section titled “Upgrade”A plain helm upgrade to the 2.12.0 image and chart, or the new tag in your Quadlet unit. Nothing happens on first start and nothing needs migrating: every instrument starts with its writes off, and there is no file until somebody turns one on. This release is amd64 first, with the arm64 build following in 2.12.1, so an arm64 box stays on 2.11.1 until then. Turning an instrument’s writes on is recorded in the audit log with who did it, so put a note on it.
Image: ghcr.io/hotloop-io/hotloop-flow:2.12.0, linux/amd64 first, with arm64 following in 2.12.1. Chart: https://hotloop.io/hotloop-flow/. The README at this tag has the rest, with pictures: https://github.com/HotLoop-io/hotloop-flow/blob/v2.12.0/README.md