Update qsrvpage.dox

Clarify use of `+meta`
This commit is contained in:
Tom Cobb
2021-10-19 12:01:46 +01:00
committed by Michael Davidsaver
parent 61ec0715be
commit 3f38e616ee

View File

@ -87,7 +87,6 @@ record(...) {
info(Q:group, { info(Q:group, {
"<group_name>":{ "<group_name>":{
+id:"some/NT:1.0", # top level ID +id:"some/NT:1.0", # top level ID
+meta:"FLD", # map top level alarm/timeStamp
+atomic:true, # whether monitors default to multi-locking atomicity +atomic:true, # whether monitors default to multi-locking atomicity
"<field.name>":{ "<field.name>":{
+type:"scalar", # controls how map VAL mapped onto <field.name> +type:"scalar", # controls how map VAL mapped onto <field.name>
@ -95,7 +94,8 @@ record(...) {
+id:"some/NT:1.0", +id:"some/NT:1.0",
+trigger:"*", # "*" or comma seperated list of <field.name>s +trigger:"*", # "*" or comma seperated list of <field.name>s
+putorder:0, # set for fields where put is allowed, processing done in increasing order +putorder:0, # set for fields where put is allowed, processing done in increasing order
} },
"": {+type:"meta", +channel:"VAL"} # special case adds meta-data fields at top level
} }
}) })
} }
@ -118,7 +118,7 @@ The "any" mapping places a variant union into which the "value" is placed.
The "meta" mapping ignores the "value" and places only the alarm and time The "meta" mapping ignores the "value" and places only the alarm and time
meta-data as sub-fields. meta-data as sub-fields.
The special group level tag 'meta:""' allows these meta-data fields to be Placing an entry in a blank field name '"": {+type:"meta"}' allows these meta-data fields to be
placed in the top-level structure. placed in the top-level structure.
The "proc" mapping uses neither "value" nor meta-data. The "proc" mapping uses neither "value" nor meta-data.