LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
marshaul

Compare Hierarchies should work properly with llbs containing libraries and dynamic dispatching

Status: New

So, I've recently transitioned portions of our code to LabView OOP. There really doesn't seem to be a feature which is equivalent to llbs in terms of how we use them, so I'm forced to build and release specific library .llbs for each class which uses dynamic dispatching. 

 

There are numerous annoyances with this, but one of the biggest is the severe reduction in the utility of the Compare Hierarchies functionality. Now, I get a all kinds of VIs which show up as "x", i.e. different, which when I pull them up show no differences at all (I always filter to show only noncosmetic block diagram changes, because who cares about anything else, really). 

 

Also, pretty much every version I get a raft of results where the only change is the path of a library/class dependency. Also, nobody cares. There should be a generation option of exclude VI path changes.

1 Comment
wiebe@CARYA
Knight of NI

@marshaul wrote:

There really doesn't seem to be a feature which is equivalent to llbs in terms of how we use them,


Can you specify "how we use them"? Most of us stopped using them 10 years ago...

 

Last I heard, it is perfectly OK to store a class and it's files in a .llb, but I haven't tried myself.

 

I've been burned by corrupt llbs so often (15 years ago) I'll avoid them at all cost.