Feature request: Being able to add a PID as a column to the fixture list pane

[unclewalter]

Okay, last one from me.

This is very much under a nice to have, but could be really powerful, especially in my case remotely managing a large number of fixtures.

In my case, I have 80 fixtures in this particular installation, all of which have some feature gates such as disabling motors or status displays. Would be excellent to be able to add that as a column to the fixture list and I can see at a glance what overrides I've put in place. Another use would be if there's a particular status code that's useful to monitor across a large group fixtures such as die temperature or certain error codes such as a homing error or overcurrent error.

Could be a context menu item given parameter in the Config, Sensors and Mfr PIDs view to be able to add to the list of available columns in the device list view. If the PID is not supported by a fixture in the list, it could just show up as a dash or empty.

[fiverecords]

Thanks — this one is worth doing properly, and I plan to include all three sources you named in the next version:

Manufacturer PIDs
Mfr PIDs tab → right-click a parameter → "Add as column to the device list". The list would gain a column with that parameter's value on every fixture that lists it in SUPPORTED_PARAMETERS. 0–1 bytes would read On/Off (per #48), numbers as numbers, ASCII as text, anything else as hex.

Sensors
Sensors tab → right-click a sensor → same menu. The column would show the present value in the sensor's own unit and precision (prefix-aware, so a centi-degree sensor reads 42.50 °C) — a die temperature across the rig at a glance.

Standard PIDs
Right-click the device list's header → "Add standard PID column…" and pick from the usual suspects: DMX fail/startup mode, lamp state, power state, lock state, display invert/level, pan/tilt invert/swap, min/max level, curve, response time, modulation frequency, burn-in, the four hours counters, factory defaults, language, identify. Values as the raw number to start with (fail mode reads 1, not "Hold"); naming them can come after if it matters to you.

Common to all three

• A fixture that doesn't have the parameter or the sensor shows a dash; one that has it but hasn't answered yet shows nothing.
• Values read once when the column is added, and again from "Refresh PID columns" in the header menu — one transaction per fixture, paced in order, so 80 fixtures is a short orderly pass rather than a burst (and together with Software brute forces PID enumeration during probing #47, nothing is asked of a fixture that doesn't list it).
• Columns persist across sessions with their width and position, and are removed from the same header menu or from the tab you added them in.

Thanks for the three reports.

[unclewalter]

Thanks for the quick replies. Those all sound like good solutions.

Look forward to the next release!