12-12-2007 04:45 AM
well you can think of a cluster as a class of data. in your case you have only one big class. all subvis will have access to all that data. it is not only aestetically a problem, but also a hierarchy one:
instead of having sets of subvis for sets of clusters, allowing for very well defined folders per cluster in your project (plus "public" vis that would treat several clusters together), you might end up having all subvis getting all the cluster. it is then much more difficult to separate the subvis into categories. very fast, expanding development might become tremendously fastidious.
12-12-2007 04:48 AM
12-12-2007 04:56 AM