Jump to content

Antoine Chalons

Members
 View Profile  See their activity

  • Posts

    955

  • Joined

  • Last visited

  • Days Won

    34

 Content Type 

Posts posted by Antoine Chalons

  3. SCC Role Call

    in LabVIEW General

    Posted

    It took me about 5 years (from 2006 to 2011) to convince people at my company to use a SCC, we use SVN + TSVN, we set up a ColabNet Subversion Edge (free) for local hosting.

    For small projects (not professional) I use Git + GitHub because I wanted to try it out, maybe one day I'll tell my colleagues about it...

  5. support for Google's Material Design

    in User Interface

    Posted · Edited by Antoine Chalons

    Not exactly, as I understand it, Material Design is not just a theme it's also about having graphical objects moving around and using the z-order to separate things.

    As far as I know we can't play with z-order of graphical object on a front panel at runtime, that in itself seems a bit limiting.

  14. Undocumented LabVIEW

    in LAVA Lounge

    Posted

    16 hours ago, CopperD said:

    Currently I am working on the thread management functions and how the IDE is notified of them so they can be aborted. At some point in time I saw a wiki but that seems to no longer exist.

    Is this what you're looking for?

  15. Where do you discuss LabVIEW?

    in LAVA Lounge

    Posted · Edited by Antoine Chalons

    On NI Forums I give help, on LAVA I seek help. I post a lot less than before but I still have a look at all the new topics and read those that relate to what I do.

    Very often when I - or someone around me - has a LabVIEW related question, I remember of a topic I saw on LAVA and give the link, the amount of great advice/help available on LAVA is huge. Couldn't live without it!

    • Like 1

  21. VI server

    in Application Design & Architecture

    Posted · Edited by Antoine Chalons

    There is no shame in asking for help, it's only if you never ask questions that you'll remain ignorant all your life ;)

     

    It's probably all about settings in the INI files next to your EXEs.

     

    Have a look at this discussion.

     

    First your 2 EXEs have to use different ports ; to set the port, use "server.tcp.port=3385" in the INI file next to your EXE

    Then the VIs in EXE A that need to be accessed from EXE B needs to be declared in the b.INI with something like "server.vi.access = "+vi_name.vi;+other_vi_name.vi;...etc..."

     

    Hope this helps

×
×
  • Create New...

Important Information

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

  I accept