Jump to content

paul_cardinale

Members
  • Posts

    70
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by paul_cardinale

  1. 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
  2. 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.
  3. 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)  
  4. Version 2.0.2.0

    27 downloads

    Installs support for Y Controls. Requires LabVIEW 2019 or later.
  5. 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
  6. Hold off on using those. New bugs have been reported. I'll have an updated version soon.
  7. 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
  8. 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. Set Property Item.vi
  9. 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.
  10. 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. Unbundle Refs By Name_xnode 1_0_0_1.zip
  11. Can you send me the entire Y Control?
  12. 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
  13. 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.)
  14. 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.
  15. 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.
  16. Is the installer creating "C:\ ... National Instruments\LabVIEW nnnn\help\Y Control\Y Controls.chm" for you?
  17. 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? Y Controls.chm
  18. 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
  19. Perhaps you might find this useful. Update File_New.zip
  20. 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
  21. I've made some minor improvements. Is anyone interested?
  22. 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
  23. 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.
  24. Gee, I put all my ideas into Y Controls. Attached is my help file (still under construction) for Y Controls. Y Controls.chm
  25. I've been developing it alone, but I'll take any help I can get.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.