paul_cardinale Posted May 19, 2021 Report Share Posted May 19, 2021 View File Y Controls Support - Version 2.0.2.0 Installer.zip Installs support for Y Controls. Requires LabVIEW 2019 or later. Submitter paul_cardinale Submitted 05/19/2021 Category General LabVIEW Version Not Applicable License Type BSD (Most common) 2 Quote Link to comment
paul_cardinale Posted June 15, 2021 Author Report Share Posted June 15, 2021 I've discovered a bug. It appears to be a bug in LabVIEW. Here is what I believe is happening: Hiding inside each instance of a Y Control is an instance of "C: ... \LabVIEW xxxx\resource\plugins\Y Control\Ability Manager\Y Control Ability Manager.XCTL". When LabVIEW loads an instance of a Y Control that depends* upon another Y Control, there are 2 instances of "Y Control Ability Manager.XCTL" that need to be initialized: One for the outer Y Control and one for the inner Y Control. The "Init" ability of the Xctl for the inner Y Control gets called first, and it works OK. However when the "Init" ability is called for the outer Y Control, it is passed the wrong refnum: Instead of getting the refnum to the instance of the Xctl in the outer Y Control, it gets a refnum to the instance of the Xctl in the inner Y Control. *In my case this happens because I have a Y Control calls a dialog VI that contains a reference to a VI that has a Y Control. 1 Quote Link to comment
paul_cardinale Posted June 17, 2021 Author Report Share Posted June 17, 2021 After a lot of digging, I found the bug (in my code). It wasn't happening just when one Y Control depended on another, but whenever two different types of Y Control were both in memory. The fix is attached. I've also done a bit of cleanup (including closing a dangling VI ref), and some minor improvements of the help. It's backward compatible; no need to rebuild anything, just run the new installer. Y Controls - Version 2.0.3.0 Source.zip Y Controls Support - Version 2.0.3.0 Installer.zip Quote Link to comment
Sparkette Posted January 28, 2022 Report Share Posted January 28, 2022 When I click "Go" on the YControl wizard, LabVIEW just sits there seemingly forever, all the while logging this error every second: <DEBUG_OUTPUT> 01/27/22 11:52:33.767 PM DWarn 0xFCC058F4: An item recompiled in the final iteration should not still have recompile needed set: [VI "Y Control Isolators and Misc.lvlib:Insert Info In Error.vim" (0x000000000a5b12a0)] /builds/labview/2021/source/compiler/compiler.cpp(643) : DWarn 0xFCC058F4: An item recompiled in the final iteration should not still have recompile needed set: [VI "Y Control Isolators and Misc.lvlib:Insert Info In Error.vim" (0x000000000a5b12a0)] [ExecSys:0; NOT InExec] </DEBUG_OUTPUT> 0x00000000006D9611 - <unknown> + 0 0x00007FFFF6DDB5F5 - _ZNK11DebugStream7ProcessEv + 25 0x000000000064D329 - <unknown> + 0 0x000000000064D991 - <unknown> + 0 0x000000000064E1B8 - <unknown> + 0 0x0000000001D14136 - <unknown> + 0 0x0000000001D15369 - <unknown> + 0 0x0000000001D18333 - <unknown> + 0 0x0000000001D1AC85 - <unknown> + 0 0x0000000001DB393D - <unknown> + 0 0x0000000002032563 - WSendEvent + 253 0x00000000020339A4 - <unknown> + 0 0x0000000001F6BABD - <unknown> + 0 0x0000000001F658F8 - <unknown> + 0 0x0000000000608599 - <unknown> + 0 0x00000000006087A8 - <unknown> + 0 0x00007FFFF6802B25 - __libc_start_main + D5 0x00000000006069F9 - <unknown> + 0 I'm using LabVIEW 2021 Community Edition on Linux. Quote Link to comment
X___ Posted July 24, 2022 Report Share Posted July 24, 2022 (edited) On 6/17/2021 at 10:20 AM, paul_cardinale said: After a lot of digging, I found the bug (in my code). It wasn't happening just when one Y Control depended on another, but whenever two different types of Y Control were both in memory. The fix is attached. I've also done a bit of cleanup (including closing a dangling VI ref), and some minor improvements of the help. It's backward compatible; no need to rebuild anything, just run the new installer. Y Controls - Version 2.0.3.0 Source.zip 1.97 MB · 9 downloads Y Controls Support - Version 2.0.3.0 Installer.zip 1.79 MB · 8 downloads If I open the content of the "Installer.zip" file, it appears to be missing the "Install Y Control Support.vi", "UNInstall Y Control Support.vi" and "Installer READ ME.txt" that you had in the 1.x version in that thread. If I copy those items in the Pure G Installer version 2 and run install, things seem to work fine. For some reason, the help file is showing a TOC but the content appears blank (same for version 1 BTW, so it might be something related to my installation in LV 2021 SP1 64 bit/Windows 10). Edited July 24, 2022 by X___ Quote Link to comment
X___ Posted July 25, 2022 Report Share Posted July 25, 2022 OK the Help file not showing its content is courtesy of MS. Simply "unblock" the chm file using Properties, 'cause: "The file came from another computer and might be blocked to help protect this computer" 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.