Function: DevicePanel()¶
DevicePanel(
props):Element
Render every property of one device, grouped and laid out as responsive cards.
Three things sit outside the alphabetical groups. The configuration
properties are not here at all: CONFIG_PROCESS is a per-device action
surface rather than a property group, so DeviceConfigDialog offers it
from the sidebar and the panel excludes it so it is not also drawn as four
anonymous buttons, and INDIKIT_CONFIG_PERSISTED is the answer that dialog
renders in words rather than as a text field full of property names. Main
Control leads, because it is where a driver puts the controls an operator
actually came for. The rest of DRIVER_MACHINERY - the driver's debug
plumbing and its snooping - folds into a collapsed "Driver internals" section
at the end, out of whichever group it was declared in.
The fold is computed from what the device has right now, so a driver that
defines DEBUG_LEVEL when debugging is switched on, and deletes it again
afterwards (which libindi does), moves it in and out of the fold on its own.
Parameters¶
props¶
The device name and an optional class name.
Returns¶
Element
The panel element.