LVOOP Class Conflict When Parent Data Edited

[James.M]

I've been using LVOOP for a relatviely large application and have a parent class named "Module" with multiple children modules. I planned it out pretty thoroughly and built from scratch, so I haven't had to make any changes to the parent Module class until now.

I added a single item to the data cluster for Module.lvclass and now 80+ VIs in my project are broken and look something like this:

The break is a Class Conflict because the dynamic dispatch terminals don't like the matchup anymore. To fix the problem, all I have to do is reroute the wire slightly causing it to recompile and realize that everything is a-okay.

Do I have to do this 80 times in order to get my application to work again? When I mass compile, the VIs that are broken like this throw a " ### Bad subVI:" in the compile log.

[James.M]

Well, upon further investigation, the solution seems to be:

1. Make change to Module
2. Mass Compile
3. Save All
4. Close Project/VIs
5. Reopen Project
6. Find one or two VIs that are still broken and manually fix the wires
7. ...Profit

I'm not sure what's going on with the few VIs that weren't fixed automatically with the rest of them, but reopening the project seemed to do the trick with most of the broken dynamic dispatch VIs. Any insight in to why this is happening evey time my parents class is edited would be highly appreciated.