10-09-2013 04:11 PM
I am always interested in workarounds and fixes! It gives me additional information to attach to the CAR to hopefully get it fixed sooner. Is it something you can post here? If that is not an option, let me know and we can find an alternative to send it.
As an aside, one of the challenges of fixing behaviors like this is that many people will have hard coded their own workarounds into their code, and depending how they coded that fix, our fix could break their code if they upgrade. This is one of the main use cases of the VI Analyzer Upgrade Tests, it helps mitigate the risk of changes like this because we can identify places in projects that might have changed behavior (something we typically try to avoid).
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments
10-09-2013 04:18 PM
Jeff,
I will post the VIs here in the next day or two. I need to dig back through what I did and make sure I documented the changes.
I appreciate the comments about upgrade compatibility. One thing which could be done at very little cost to NI and with no risk to legacy code is to document in the help files exactly what the behavior is.
Lynn
09-14-2015 06:07 PM
Any chance I can get that workaround you mentioned? I know it has been a few years now, but the problem seems to persist in LV2014.
thanks,
Matt