You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With open62541 1.3 and before, the generated UA_DataType values had the hardcoded namespace index from the NAMESPACE_MAP parameter in their typeId and binaryEncodingId fields.
For 1.4, the UA_DataType values are generated with namespace index 0 for these fields and the appropriate index is set by a for-loop in the namespace initialization function for the server.
This takes care of the server side, but adding the custom types to the client config as in 1.3 fails to decode the custom types due to the wrong namespace index.
Is there an official/documented way to set the namespace index in all members of a generated types array before adding it to a client config?
The text was updated successfully, but these errors were encountered:
With open62541 1.3 and before, the generated
UA_DataType
values had the hardcoded namespace index from theNAMESPACE_MAP
parameter in their typeId and binaryEncodingId fields.For 1.4, the
UA_DataType
values are generated with namespace index 0 for these fields and the appropriate index is set by a for-loop in the namespace initialization function for the server.This takes care of the server side, but adding the custom types to the client config as in 1.3 fails to decode the custom types due to the wrong namespace index.
Is there an official/documented way to set the namespace index in all members of a generated types array before adding it to a client config?
The text was updated successfully, but these errors were encountered: