Jump to content

El_Frito

Members
  • Posts

    2
  • Joined

  • Last visited

El_Frito's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I've built a Labview interop assembly from a project, and I need to pass in a .Net object to a VI as an input parameter. I'm calling it from C# code, and the metadata shows the function needs an 'LVReferenceNumber' type to represent the .Net reference. I can't figure out how to create this structure from my .Net object. Example (this would create a .Net object and pass it into a VI call): MyObject Obj = new MyObject();NationalInstruments.LabVIEW.Interop.LVReferenceNumber lvRef = (LVReferenceNumber)Obj;MyInteropAssembly.LabVIEWExports.MyVI(lvRef); Obviously the cast does not work--does anyone know how to create this LVReferenceNumber from my .Net object? Thanks
  2. I'm creating an application which has a relatively small main screen and switches between recording, playback, and several monitoring modes. My approach was to create a sub panel and swap out the front panels of several sub vis running in parallel. I've got an event structure in the main vi that will pass user events to the sub vi event structures to let them know when they're being displayed. Every sub vi event structure uses the same user event registration. This works well... 95% of the time. Once in a while (I haven't found any consistencies, yet) a user event does not get handled. For instance, when the user clicks on the "New Recording" button on the main panel, the main panel's event structure generates a user event that should inform the 'new recording' sub vi to pop up the recording wizard. Once in a while.. no wizard. Another example (a more serious one) is when the "Exit" button is pressed, one of the sub vis will not exit. The particular vi which does not exit is not consistent--sometimes its the 'new recording' sub vi, sometimes its the 'status monitor' sub vi, and so on. I've dropped in debugging scenarios which should alert me if there is an error that could be being dropped, but I haven't found anything so far. Is there something that could cause the user event to not be handled? Thanks
×
×
  • Create New...

Important Information

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