
paul_cardinale
-
Posts
70 -
Joined
-
Last visited
-
Days Won
10
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by paul_cardinale
-
-
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
-
-
Y Controls Support - Version 2.0.2.0 Installer.zip
-
Submitter
-
Submitted05/19/2021
-
Category
-
LabVIEW VersionNot Applicable
-
License TypeBSD (Most common)
-
2
-
-
Here is the fixed version (also a bit of cleanup and some tweaks to the help. Unfortunately you will have to recreate your Y Controls (but if you really need to keep any that you made with V2.0.1.0 or V2.0.0.0, contact me and I'll help you.
Y Controls Support - Version 2.0.2.0 Installer.zip Y Controls - Version 2.0.2.0 Source.zip
-
Hold off on using those. New bugs have been reported. I'll have an updated version soon.
-
Here is version 2. As far as I know, there are no issues with it Requires LabVIEW 2019 or later. Not compatible with earlier versions.
Y Controls Support - Version 2.0.0.0 Installer.zip Y Controls - Version 2.0.0.0 Source.zip
-
1
-
-
The SetProperty method still doesn't support dotted property names in LV 2020. Using the attached VI will allow for a smooth transition if SetProperty is every upgraded.
-
Based on the lack of feedback, I infer that there's little or no interest. But I've been using Y Controls, finding issues, and fixing them. Since no one else appears to have been participating, I haven't concerned myself with backward compatibility, I'm getting close to sharing a new version. Anything made with the old version will be broken.
-
1
-
-
This is a named unbundler for clusters; but instead of taking in a cluster value and outputting element values, it takes in a reference to a cluster and outputs references to elements.
Sadly, it can't handle a cluster containing a latching boolean.
-
1
-
-
1 hour ago, X___ said:
LV 2019 SP1f1 64 bit crashed upon closing my first Y Control... but seems to have recovered fine.
So, I can now resize objects within a Y Control cluster, but there seems to be a glitch (race conditions?) in the Process New Value.vi:
When the user changes the checkbox (for visibility) to True, the string is hidden and reciprocally. Am I missing something?
Can you send me the entire Y Control?
-
Quite a few changes: Cleanup, bug fixes, and kludges to workaround a bug in LV 2018 and earlier (but the installer is smart enough not to include the kludges when installed with LV 2019 +).
If you've made any Y Controls with the prev version, you'll need to remake them.
Y Controls Version 1.0.0.3 Source.zip Y Controls Support Version 1.0.0.3 Installer.zip
-
Here's another one: If the owning VI is set to run when opened, it will start running before the Y Control finishes initializing. (I might have to do some major surgery to resolve this.)
-
Is anyone else running into bugs? This one is driving me nuts: If the owning VI is a member of a library, and the library is open, then the event handler usually doesn't launch.
-
Perhaps this is the problem: When changes are made to LV help, they don't take effect until LV is restarted,
I'll improve the completion dialog for the installer.
-
12 hours ago, X___ said:
1. I removed LVNewDialog.xml before re-installing 1.0.0.2 and got this:
which, after I pressed continued, left the installer window opened in a stopped state, but at least now the help is back in the menu (but in Help>>Y Control, not Help -> New -> Y Control as you have it in the Readme.txt)
However, the File>>New... dialog is now empty, so removing LVNewDialog.xml is definitely not the thing to do (putting it back resolves the issue but is missing the Y Control item).
2. Re-uninstalling Y Control Support now LEAVES the Help >> Y Control menu but nothing happens when selecting it:
3. Re-reinstalling 1.0.0.2 restores the Y Control item in the New... dialog box...but removes the Help menu!
Getting somewhere?
Is the installer creating "C:\ ... National Instruments\LabVIEW nnnn\help\Y Control\Y Controls.chm" for you?
-
2 hours ago, X___ said:
Still can't seem to be able to access the Help. Certainly not in the Help -> New -> Y Control -> Y Controls menu and the chm file still doesn't work for me?
It seemed quite straightforward when I first installed it, but maybe the UNinstall step messed up with something?
I just uninstalled 1.002 and tried again the release from post 22 and am without an easy way to find Help within LV (and the chm file is not working anymore as a standalone) 😞
Uninstall deletes "C:\ ... National Instruments\LabVIEW nnnn\resource\plugins\Y Control\*", "C:\ ... National Instruments\LabVIEW nnnn\help\Y Control\Y Controls.chm", and removes the Y Control from "C:\ ... National Instruments\LabVIEW nnnn\resource\plugins\NewDialogFiles\ LVNewDialog.xml".
Is the installer creating "C:\ ... National Instruments\LabVIEW nnnn\help\Y Control\Y Controls.chm" for you?
-
There were some missing dependencies in the source zip. I also renamed a library to make name collisions less likely.
Y Controls Support Version 1.0.0.2 Installer.zip Y Controls Version 1.0.0.2 Source.zip
-
On 11/25/2020 at 10:44 AM, The Q said:
I just added an explanation of how to add to the New dialog on the LabVIEW Wiki:
https://labviewwiki.org/wiki/New_dialog
If you have any ideas to help me make QControls better, let me know. I have a thread on the QControl Enthusiasts page:
Perhaps you might find this useful.
-
That issue has been corrected (see attached files). However it won't fix already-created Y Controls. To fix them, make sure that Facade.ctl and the .yctl file are set as "TypeDef" and not "Strict TypeDef"
Other improvements:
- The installer and uninstaller will ignore RO status of an existing installation of Y Controls.
- The wizard fixes up the label of the cluster in the .yctl file.
Y Controls Support Version 1.0.0.1 Installer.zip Y Controls Version 1.0.0.1 Source.zip
-
I've made some minor improvements. Is anyone interested?
-
Unzip the installer, read the READ ME, run the installer, read the help (LabVIEW -> Menu -> Help -> Y Controls).
If you're curious, look in the source.
Y Controls Support Version 1.0.0.1 Installer.zip Y Controls Version 1.0.0.1 Source.zip
-
1
-
-
On 11/25/2020 at 2:36 AM, Antoine Chalons said:
This looks interesting, I've created a QControl and really enjoyed the concept, haven't dug too much into Y controls but it looks interesting, are you developing this alone or as an open source project?
I get the same error when building the VIP, you should post here I think : https://forums.jki.net/forum/5-vi-package-manager-vipm/ to get some support, JKI is usually quite responsive.
I managed to post the issue there, but it's very cumbersome because I only get one post per password reset (and their Contact Us link is broken). I did get a reply and was able to solve that problem, but now it throws error 1357. Maybe it's time to throw in the towel on VIPM.
-
4 hours ago, The Q said:
I just added an explanation of how to add to the New dialog on the LabVIEW Wiki:
https://labviewwiki.org/wiki/New_dialog
If you have any ideas to help me make QControls better, let me know. I have a thread on the QControl Enthusiasts page:
Gee, I put all my ideas into Y Controls. Attached is my help file (still under construction) for Y Controls.
-
I've been developing it alone, but I'll take any help I can get.
-
Sometimes I get this (which makes no sense because that VI is not a dependency of Y Controls, and it is not missing)
[CR] Y Controls Support - Version 2.0.2.0 Installer.zip
in Code Repository (Certified)
Posted
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