Keys location within Clusters

6 posts / 0 new
Log in or register to post comments
Last post
Wed, 10/02/2013 - 07:47
#1
johnk
johnk's picture
Offline
Last seen: 9 years 1 week ago
Joined: 09/10/2013
Posts: 4
Keys location within Clusters

LabVIEW 2013; WIndows 7 AGM; LabeVIEW Integration 1.0.0.87

If one has a cluster that contains other clusters, must the key ALWAYS be contained in the top level Cluster

This works, when the key is contained in the top-level

ClusterType OuterCluster
{
   data;                            <Can use as key!!!  :)
   InnerClusterType InnerCluster
   {
        data;
   }
}

However, it doesn't seem to work if the key is contained within a cluster.

ClusterType OuterCluster
{
 InnerClusterType InnerCluster
   {
        data;                       <Can't use as key :(  (or can't figure out the proper access syntax)
   }

 InnerClusterType2 InnerCluster2
   {
        data;
   }
}

Otherwise, our port from reflective memory to RTI Connext DDS is almost complete, thanks.

JohnK!

Keywords:
Top
Wed, 10/02/2013 - 09:08
sara
sara's picture
Offline
Last seen: 1 year 4 months ago
Joined: 01/16/2013
Posts: 128

Hi JohnK!

I've been able to reproduce it with the shipped examples. I'll take a look and give you more details about what's going on.

All the best,

Sara

Top
Thu, 10/03/2013 - 11:34
sara
sara's picture
Offline
Last seen: 1 year 4 months ago
Joined: 01/16/2013
Posts: 128

Hi again JohnK!

Sadly, this issue is related to the current limitation of one key in the RTI DDS Toolkit for LabVIEW. To make DDS understand that a field inside a structure is a key, you have to mark that struct as a key in the top level structure. So it would be something like:

struct InnerClusterType {
    int data; //@key    <-- If you want to mark this one as key...
}

InnerClusterType2 {
    int data;
}

ClusterType OuterCluster {
    InnerClusterType innerCluster; //@key    <-- ... you need to mark this one too.
    InnerClusterType2 innerCluster2;
}

As you can see, to define that you need to mark two fields as a key, something that it's currently not supported. We plan to support this soon (most likely next release). Once the new release is available, you will find the RFE code "LABPLG-17" into the "What's new" section of the Release Notes document.

If you need more information about the release or this is a priority for you, contact us and we'll work with you to make you successful :)

All the best,

Sara

Top
Tue, 02/18/2014 - 08:57
JayC
Offline
Last seen: 2 years 6 months ago
Joined: 10/18/2013
Posts: 42

Are multiple keys supported in 5.1?

Top
Tue, 02/18/2014 - 09:29
sara
sara's picture
Offline
Last seen: 1 year 4 months ago
Joined: 01/16/2013
Posts: 128

Hi JayC,

We are currently working on a new version of the RTI DDS Toolkit for LabVIEW (version 1.1.0.x) that will be compatible with RTI Connext 5.1. This version will be released soon and will contain, among other improvements, the multiple key support.

Thanks,

Sara

Top
Thu, 03/20/2014 - 11:09
sara
sara's picture
Offline
Last seen: 1 year 4 months ago
Joined: 01/16/2013
Posts: 128

Hi again,

This problem has been fixed in the latest release of the RTI DDS Toolkit for LabVIEW (version 1.1.0.88), compatible with RTI Connext 5.1. In this release multiple keys can been provided to the Create subVIs. 

You can download the new version using the VIPM.

Thanks,

Sara

Top