Before a memory device is set to a value, it is "typeless". In other words, if a client tries to read a memory device that has never been set, it doesn't know what type it is. This is a problem in the DrMem browser app. When the browser receives the first value from a device, it knows the type and creates appropriate widgets to view and set it. But with memory devices that haven't been initialized, it doesn't know what setting widget to use. This means, when you create a new memory device, it's difficult to set its first value (I end up using a GraphQL client.)
The current driver only allows one variable to be created per driver instance. If a site uses many memory devices, the config file can get quite large and confusing.
To fix these problems, this issue proposes to change the driver configuration and driver itself. The base config key will be vars and it will return an array of maps. In the maps are two keys, name and initial. name takes a String and represents the name of the memory device. initial can take any value DrMem device value. If the memory device has not yet been set, this value will be immediately reported.
All the variables will be handled by the one instance.
Note that all variables defined in one instance of the driver will have the same path prepended to their names. If different paths are desired, then multiple instances of the driver will have to be used.
rneswold
commented
5 months ago
The memory driver has two deficiencies:
To fix these problems, this issue proposes to change the driver configuration and driver itself. The base config key will be
varsand it will return an array of maps. In the maps are two keys,nameandinitial.nametakes aStringand represents the name of the memory device.initialcan take any value DrMem device value. If the memory device has not yet been set, this value will be immediately reported.All the variables will be handled by the one instance.
Note that all variables defined in one instance of the driver will have the same path prepended to their names. If different paths are desired, then multiple instances of the driver will have to be used.