Jump to content

jgcode

LabVIEW Tools Network
  • Content Count

    2,397
  • Joined

  • Last visited

  • Days Won

    66

jgcode last won the day on August 15 2019

jgcode had the most liked content!

Community Reputation

322

1 Follower

About jgcode

  • Rank
    LabVIEW Renegade

Profile Information

  • Gender
    Male
  • Location
    Australia

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2009

Recent Profile Visitors

14,668 profile views
  1. Nice. Are you able to post any example code? Cheers
  2. Nothing from me but I would still love a wrapper for this functionality from NI
  3. Hi Shoneill, are you able to provide details of are planning? This code is 2012, open source, and includes a modification of the library references above (creates a wrapper around a delegate class).
  4. I changed my thinking on this a while ago too Reads can be as simple as one in and one out: LVOOP Object input, accessor-data-item output
  5. Just had code that worked in development but returned a 1502 build error (cannot Save A Bad Vi Without Its Block Diagram) Hunted it down and turned out to be a privately-scoped VI in a polymorphic API Changed to public and all good
  6. I would say the most important thing is to give it a go and find out As for me, I find it easy but more importantly fun to use! Also, I like creating an API that uses the event structure to communicate with a process and this compliments it well
  7. Ok, so its not all AppRef functions that are effected, just the one in this post That's a relief
  8. Howdy I am chuffed to be giving away an AudibleListener® 6-Month Gold Gift Membership. Sure beats reading
  9. Hi Mikael, I include all library files in my VI Server script as well, but I am insure as to what that option actually does. It seems the global settings (LabVIEW options or project options) override when a VI/ctl is added to a library (LV2012) making me think it is redundant or a bug. Do you know setting the library to separate compiled code does?
  10. That sounds like too much hard work - lol You can bulk mark VIs through the project's options or you can use VI Server and script it I tried this feature out recently and liked developing with it One thing I concluded with tho is that if I ship a tool (essentially a source code dist) I want to install compiled code with it Otherwise the tool needs to be compiled for use in its native version of LabVIEW VIPM can do this on install, or the tool can also recompile itself, but IMHO it makes for a better UX (quicker install and first launch) This was easily achieved using VI Server
×
×
  • Create New...

Important Information

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