Michael Aivaliotis Posted November 25, 2015 Report Share Posted November 25, 2015 This is is LabVIEW 2015. Haven't tried in other versions but I assume it also fails as badly since it's not really a LV2015 feature. Here's my dialog configuration: Basically what happens most of the time is it just creates the property folder and 2 read\write VIs that are incompletely scripted: I have to remove the property folder and the VIs from the class and redo the dialog. Sometimes 3-4 times before it finally works. There doesn't seem to be a pattern to this. Has anyone else experienced this? if so, I guess I should report it to NI. If this is already mentioned on another thread, then sorry for the noise. Quote Link to comment
LogMAN Posted November 25, 2015 Report Share Posted November 25, 2015 (edited) This works fine on my computer (tried it at least 10 times). Do you have the same issue on a clean project? EDIT: Could you upload an example which fails on your computer? Edited November 25, 2015 by LogMAN Quote Link to comment
PiDi Posted November 25, 2015 Report Share Posted November 25, 2015 The only time I've seen it broken like that is when I broke it myself when playing with Custom User Scripting for accessors. This is just a shoot in the dark, but check your <LabVIEW>\resource\Framework\Providers\LVClassLibrary\NewAccessors\BaseAccessorScripter\Custom User Scripting For New Simple Accessor VI.vi - by default its BD is empty. Quote Link to comment
Michael Aivaliotis Posted November 25, 2015 Author Report Share Posted November 25, 2015 Perhaps there's an error generated somewhere that i can probe? Quote Link to comment
PiDi Posted November 25, 2015 Report Share Posted November 25, 2015 Oh, yes you can: put breakpoint in <LabVIEW>\resource\Framework\Providers\LVClassLibrary\NewAccessors\BaseAccessorScripter\CreateBaseScripter.vi. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.