Jump to content

Michael Aivaliotis

Administrators
  • Posts

    6,196
  • Joined

  • Last visited

  • Days Won

    104

Posts posted by Michael Aivaliotis

  1. I would think that source distribution is your best bet. If you don't like the detailed hierarchy then you may use llb as your destination. You can put each class into separate llbs.

    If you want to use the EXE method that I think you would need to run the EXEs and communicate to them with an application reference mechanism and VI server calls. Not sure what you did exactly in the EXE implementation.

    • Like 1
  2. I use methods and properties on the diagram all the time. However, I also use clusters or arrays of ctrl references passed into subVIs as well.

    I don't think it's a good idea to manipulate UI objects from within a class unless the main purpose of that class is to manipulate the UI. Like a UI class.

    In your example, I would create a method called Engine State. I would read that state, and if the engine was running, I would disable the button.

    • Like 1
  3. Ok, now I have a new problem that comes under the topic heading. The file uploader is failing to upload my files... I select the file on my computer, I get the progress bar and then it comes to the end saying that the upload failed. I've tried Firefox and IE8 and also checked that it doesn't make a difference whether I access the local file via system Library or direct path (Win 7 64bit). So now I'm a bit stumped for ideas.

    Please try now. It's fixed. There was a glitch due to the recent server upgrade.

  4. What version of LabVIEW did you upgrade your current LabVIEW application from? I assume it was working before (on the previous LV version) and now it's not working?

    How are you testing this on older LV versions? Are you down-saving the VIs?

    When you say the DLL returns all the correct info. How is that possible if it cannot communicate with the hardware? What is returned?

×
×
  • Create New...

Important Information

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