06-18-2019 10:09 AM
Really stupid question: Is the Control disabled on the FP?
Right-click - Advanced - Enabled State ?
06-18-2019 10:13 AM
@Intaris wrote:
Really stupid question: Is the Control disabled on the FP?
Right-click - Advanced - Enabled State ?
It doesn't like that game
06-18-2019 10:25 AM
Ah. Because you have data there which isn't the default class data, it may actually be of a child instance which is no longer in memory. But surely that would prompt for loading the child on loading the VI? I dunno. LabVIEW is weird sometimes.
06-18-2019 10:49 AM
Can you throw a probe on it an run it to see what it's defaulting to? Like Intaris said, maybe it's a child class. Maybe the probe will show some more info?
06-18-2019 11:31 AM
@deceased wrote:
@Intaris wrote:
Really stupid question: Is the Control disabled on the FP?
Right-click - Advanced - Enabled State ?
It doesn't like that game
If you first make the class control a TypeDef then you can enable or disable it from that menu. If you then immediately Disconnect it from the TypeDef you are stuck in the enabled/disabled state that you set.
06-18-2019 12:25 PM
@Intaris wrote:
Ah. Because you have data there which isn't the default class data, it may actually be of a child instance which is no longer in memory. But surely that would prompt for loading the child on loading the VI? I dunno. LabVIEW is weird sometimes.
I think this is an interesting thought. Looking at the class, this code is extended by a child. In the application it's always the child on the wire (it just does its bit then calls parent).
I wanted to check the theory, but attempting to run it went badly. Complete IDE crash : DAbort 0x0037C03D in MemoryManager.cpp
I'm thinking I should just replace these and move on with my life. Unless anyone else has any further insight.
06-18-2019 01:15 PM - edited 06-18-2019 01:19 PM
I had no issue setting child class data as default and then completely nuking the child class. No errors, no problems. The data is sliced as expected.
The only way I can get grayed out class controls with an unbroken VI is by disabling. This can be done by making the control a typedef temporarily, using the Property Node, or using the Properties dialog. If you right-click the control and select Properties does it show as Disabled and grayed out?
06-18-2019 01:28 PM - edited 06-18-2019 01:33 PM
Darin, properties for this one shows enabled.
Edit: Interestingly, if I set it to disabled and grayed, it gets grayer.
Here "in" is disabled and grayed
06-18-2019 01:31 PM
Kill them all and move on before they corrupt more of your code...
06-18-2019 01:35 PM
Thanks for all the suggestions. I think I will follow Darin's advice and burn them with fire.