Jump to content

PJM_labview

Members
  • Posts

    784
  • Joined

  • Last visited

  • Days Won

    10

Posts posted by PJM_labview

  1. QUOTE (normandinf @ May 12 2009, 07:02 PM)

    And you can set input values using the OpenG tools before using the "Run VI" method. That's the way I use my plugin VIs.

    I agree, the CBR is way too strict (no pun intended). I also prefer to use the run method, but I would even consider using other mechanism to pass the data to the plugin (than the set input value). The goal being to limit code change when the plugin interface changes.

    By the way, if you use CBR, just create a control with the right type (connector pane) on your plugin caller and you will be ok. Of course all your plugins must have the same connector pane in that situation.

    PJM

  2. QUOTE (neBulus @ May 1 2009, 06:49 AM)

    I have had many questions about what the profiler shows me in recent version as well.

    Run some benchmark tests to see if they confirm what the profile is showing.

    Ben

    I have had a lot of questions about the profiler since LV 8.0. I believe something was changed somewhere so that it does no longer behave quite the same way that in previous LV version

  3. I still have mine with the original box (a bit battered though) and all the documentations that came with it. Additionally I have 2 extensions card in it (32 and 128k).

    post-121-1240336101.png?width=400

    If I were to sell it I seriously doubt I would make money. I bough it in France and it was very expensive at the time.

    Oh, and I also still have a C64 (sadly no longer functioning, although I believe the floppy drive is still working).

    PJM

  4. Another possibility (convoluted but it should work):

    Create a SubVI that does the following:

    • Create a batch file in windows temp folder (reuse the same name every time so you don't end up creating many batch files ) that will wait a bit (1-2s) before deleting your ini file.
    • Execute this batch file using system exe (non blocking).

    Note: you should run this SubVI as the last operation you do before exiting your app.

    PJM

  5. QUOTE (Cat @ Apr 3 2009, 11:06 AM)

    Don't get me wrong -- I love state machines and use them all over the place. I just never made the leap into using it to make more simplified transitions between parts of my code that *always* go step1->2->3->etc.

    And the beauty of having it in a frame of the state machine is that the day you need to call that init frame back (when not doing per say an init step [this does occurs on occasion especially for UI stuff]) you can easily do that without creating duplicate code.

    PJM

  6. QUOTE (Aristos Queue @ Mar 26 2009, 04:20 PM)

    All of the above is true through LV 8.6. The next version of LV this will all be mostly true, but we're making some architecture changes... they will be mildly beneficial to performance in the next LV version... and they open sooooo many intriguing doors...

    Would that be the DFIR (Data Flow Intermediary Representation) stuff that Jeff K. talk about in last year NIWeek keynote presentation? Anything you could share with us?

    PJM

×
×
  • Create New...

Important Information

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