Leaderboard

I'm having a separate GChat about this issue, and will copy what I just wrote moments ago: "the main prob is that filenames (rather than embedded GUIDS) are used as identifiers in class hierarchies. it's frustrating. same thing bites you with Dynamic Dispatch VIs -- they must have the same filename (which I personally find annoying)... filenaming convention should be abstracted from class functionality" So, I think we're independently coming to the same conclusions here, crelf *** EDIT: and this is not a bash against the current convention, I'm sure it exists for good reason. It's just that I'm running into problems, and just trying to flesh out the best practice ***

Here is the MCL control again (since the previous links in the Thread are broken). Thanks special MCL.vi

I'd say it's just showing us the weakness of the by-name tethering that occurs between classes. Maybe it's time (for NI) to consider having something else idenitify classes to each other - perhaps some kind of GUID? We'd, of course, need some way to override it to be able to continue to distribute additional classes as plugins, but I'm thinking the name and prototype of the classes is a little too restrictive.

I believe this is what jpdrolet had in mind: