Automatic inlining of class accessors

[cirrusio]

It seems that now (I am guessing this was introduced in 2015) we have automatic inlining of object accessors.  

I didn't realize this was a thing until I was struggling with a build and found that I could not debug the accessor (seems trivial but was necessary).  I am now concerned that this may be a factor in some builds that are not good, but see no way to turn this automatic inlining off.  Am I missing something?

[WenR]

Hi cirrusio

I would like to confirm: with "but see no way to turn this automatic inlining off" do you mean switching this off by default for any new blank VIs? If there is a way to do this, it is probably in the ini file or using VI templates. I'll look into this and give you an update tomorrow. 

If this is not what you meant, please let me now!

WenR

[cirrusio]

Ya...this is exactly what I mean.  

[WenR]

Matt

Thanks for the confirmation. I am sorry for the delay. I didn't find any tokens we can use in the LabVIEW INI to change this configuration. While testing with tokens that might do the work, I noticed that the default setting was FALSE in my case. I tried in other computers with LV 2015 and I got the same result. I then did a fresh new install of LV 2015 and LV 2016 and I also got FALSE as the default setting, so I am afraid to say that this behavior might be something limited to the particular computer that you have.

I would try deleting the LabVIEW INI file to see if it helps, I've seen a lot of weird and hard to explain behaviors get fixed that way. If that doesn't help, creating a VI template with this option disabled. For anyone who is not familar with VI Templates, saving a blank VI with that option disabled as .vit would do the trick.

WenR