MathWorks

Hello,

Hello,

Is there an API that can be used to determine if a type has been previously registered via DDS_DomainParticipantFactory_register_type_support()?

Thanks.

Mark.

I am using the Dyanamic Data API's to send/receive toipcs with unions.  I have 3 questions about the proper way to handle the discriminator value when read/take a sample that contains a union. The descriminator value is needed in order for the data reader application code to know which field in the union data structure has valid data.

Hello,

Hello,

Is there an API what will give me the IDL-equivalent for a DDS_TypeCode that has been previously registered?  Since the Admin Console can display IDL information, I assume this is possible but haven't been able to find appropriate function.

Thanks.

Mark.

There are existing API's for accessing QoS libraries and profiles ( DDS_DomainParticipantFactory_get_qos_profile_libraries(), DDS_DomainParticipantFactory_get_qos_profile()).

Are there similar functions for loading <types>, <domain_library> and  <domain_participant_library>?  I searched through doc and header files but can't find anything.

Thanks.

I have an application that uses read_next_sample()/take_next_sample().   What is the proper way for the application to determine if a valid sample has been read/taken.  Does return value of DDS_RETURN_OK indicate a valid sample?  Or must SampleInfo.valid_data also be checked before using the sample data?

Hello

Is there a DataReader StatusCondition, ReadCondition or QoS policy that will allow DataReader to only return a sample when the contents of the sample have changed?

Thanks.

I make extensive use of the DynamicData API for registering, reading and writing TopicData.  I have relied on examples provided in this Forum and the Knowledge Base to handle sequences, nested structs, enums, etc.  However, I have recently run into a problem with a topic whose definition includes typedefs.  My code fails when encountering a member in DDS_DynamicData that was defined in the IDL file with a typedef.  It appears that the _type._data fields are not valid for a typedef, but rather the information in _type._data._typeCode should be used.