@Mike_Le wrote:
Is the LabVIEW 2020 error window also less of a resource hog? The window is so slow to respond in large applications if it thinks half the project's broken due to a single messed up VI/class.
We have improved the performance of that window, but maybe not in the way you're asking.
Usually the "slow to respond" is when the VI goes from bad to good and lots of VIs try to recompile all at the same time. The recompile work isn't needed until you actually run the VIs, so we moved that to not be synchronous with the editor. That helps considerably in LV2020.
But you're talking about it being a drag when the VIs are broken. I believe you, but I haven't seen that myself and don't have any bug reports to that effect. So, no, we haven't done anything to investigate the Error List window's performance. If you have a hierarchy that shows the problem, please share it with NI.
The Hierarchy Window -- that's a resource hog. My team did do some work this release to pull that down, but it's still a drag on the system when it is open.
