Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/30/2010 in all areas

  1. Watch out for Mr. Bookman
    1 point
  2. I apologise in advance for this, but it's something I saw a couple of years ago, and we're all thinking it:
    1 point
  3. While there is no consistent implementation of refnums in LabVIEW there is one specific thing an LVRefNum has always been, and most likely stays in 64Bit too, and that is its implementation as a MagicCookie as shown in the LabVIEW CINtools headers. Here you can see in extcode.h typedef uInt32 MagicCookie; completely independant of the bitness of LabVIEW so it seems to be a safe assumption for now that the data part of refnums correspond always to a 32Bit value. There is of course a wrench with this, since the so called Tag based refnums, like VISA, DAQmx, etc refnums also consist of a string part identifying the actual resource a refnum refers too, but even those refnums use internally a MagicCookie too.
    1 point
  4. The ability to replace the NI editor with a custom one wasn't implemented until LV8. I do have an Icon editor that will run in Windows with LV7.0. It runs inside another shell vi called the (Subvi fixer) I'll try and dig it up and post it but it may take me a day or so. Mark
    1 point
×
×
  • Create New...

Important Information

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