Jump to content

paul_cardinale

Members
  • Posts

    84
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by paul_cardinale

  1. Version 3.0.1

    11 downloads

    Of course I had to break something in 3.0 (the help links) just before I submitted it. While I was at it, I reorganized the help a bit. Also patched up the installer so it gets rid of old leftovers.
  2. View File EXIF Reader V3.0.1.zip Of course I had to break something in 3.0 (the help links) just before I submitted it. While I was at it, I reorganized the help a bit. Also patched up the installer so it gets rid of old leftovers. Submitter paul_cardinale Submitted 11/07/2023 Category *Uncertified* License Type BSD (Most common)  
  3. Version 3.0.0

    2 downloads

    Version 3. Has bug fixes, enhancements, additions.
  4. View File EXIF Reader Version 3. Has bug fixes, enhancements, additions. Submitter paul_cardinale Submitted 11/07/2023 Category *Uncertified* License Type BSD (Most common)  
  5. Version 1.0.1

    5 downloads

    Fixed some bugs in the installer. fixed
  6. View File EXIF Reader - V1.0.zip Fixed some bugs in the installer. fixed Submitter paul_cardinale Submitted 09/28/2023 Category *Uncertified* License Type BSD (Most common)  
  7. Version 1.0.0

    8 downloads

    This EXIF Reader contains VIs for reading EXIF metadata in image files. Most of the VIs are to be called as sub VIs, but some are intended to be used as top level VIs, and one can be used either way. This S/W can currently read EXIF data from .jpg, .mpo, and .png files; but this user extensible. Note however that there are no hooks in the S/W for parsing out data sets whose contents vary from brand to brand
  8. View File EXIF Reader - V1.0.zip This EXIF Reader contains VIs for reading EXIF metadata in image files. Most of the VIs are to be called as sub VIs, but some are intended to be used as top level VIs, and one can be used either way. This S/W can currently read EXIF data from .jpg, .mpo, and .png files; but this user extensible. Note however that there are no hooks in the S/W for parsing out data sets whose contents vary from brand to brand Submitter paul_cardinale Submitted 09/26/2023 Category *Uncertified* License Type BSD (Most common)  
  9. Is there really a menu command that would invoke the font dialog? What would it be?
  10. Do you know of a way to invoke the font dialog?
  11. This seems to work OK. But the Mac version is rather slow. Get Font Names.vi
  12. Unfortunately, "Get Font Names.vi" doesn't work properly on a Mac: The list returned includes names of fonts that aren't available, and is missing some that are available.
  13. Here's what I came up with. Don't know if the Unix target works. Get Font Names.vi
  14. Aggg! I can't remember how to get a snippet from LAVAG. What's the trick?
  15. 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
  16. 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.
  17. 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)  
  18. Version 2.0.2.0

    119 downloads

    Installs support for Y Controls. Requires LabVIEW 2019 or later.
  19. 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
  20. Hold off on using those. New bugs have been reported. I'll have an updated version soon.
  21. 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
  22. 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
  23. 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.
  24. 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
  25. Can you send me the entire Y Control?
×
×
  • Create New...

Important Information

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