We are using Eta C API to implement views functionality using ACRONYM. TransportAPI_C_DevGuide.pdf document stated that RDM_VIEW_TYPE_ELEMENT_NAME_LIST can be used. However, I am seeing that all fields are returned. May I know why? Below are snippet of incomplete codes to get general idea of what's I am attemping to implement:
eEntry.dataType = RSSL_DT_UINT;
fdList = RDM_VIEW_TYPE_ELEMENT_NAME_LIST;
transport.rsslEncodeElementEntry(encodeIter, &eEntry, &fdList);
transport.rsslClearElementEntry(&eEntry); eEntry.name = RSSL_ENAME_VIEW_DATA; eEntry.dataType = RSSL_DT_ARRAY;
transport.rsslEncodeElementEntryInit(encodeIter, &eEntry, 0)
viewArray.primitiveType = RSSL_DT_ASCII_STRING;
viewArray.itemLength = 0;
transport.rsslEncodeArrayInit(encodeIter, &viewArray)
transport.rsslEncodeArrayEntry(encodeIter, NULL, &viewList[i])
transport.rsslEncodeArrayComplete(encodeIter, RSSL_TRUE)
Hi @tinmyo.win,
While the API does have a flag defined to allow the specification of named fields, I believe at this time the ADS only supports field IDs. You can refer to this answer for more details.
ETA: request a view, but get an error: State: Open/Ok/Invalid view - text: "All is well"
Login StatusMsg in ETA MRN tutorial
Why SEQNUM is in order but QUOTIM_MS is not?
What could cause state to become RSSL_DATA_SUSPECT and RSSL_STREAM_CLOSE for valid symbols?
Elektron Transport API Java Application Got Disconnected Randomly