Jump to content

tnt

Members
  • Posts

    86
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by tnt

  1. Take a look at the attached program and see if it helps. These are the only three properties that I know of that will control the size and location of a graph while the program is executing.

    I had a similar problem at one time.

    Hi,

    I just can't find the Plot Bounds (short names) / Plot Area Bounds (long names) property. :wacko:

    Do you have scripting enabled?

    Can you show where to find it?

    With kind regards,

    TNT

  2. Hello,

    a while ago I've made a subvi that is able to get all controls of the toplevel-VI.

    This has been accomplished by getting all the controls[] refnums and then cycling

    through all the clusters/tabs/arrays to get an array of all refnums (only controls).

    Then when 1 of these items gets the keyfocus (cycle entire array), a popup-keyboard will appear.

    Now in a new project (still LV 7.1.1) I started using subpanels and noticed that

    the controls on the subpanel are not accessible when starting from the subpanel refnum. :headbang:

    (casting of a refnum to VI-type fails, casting to subpanel / paneltype does not give

    any access to a controls[]-property.

    As a workaround I've called the controls[]-property directly from the VI-refnum that is started in the subpanel,

    but I really would like to reach these properties starting from the top-level-VI-refnum.

    Is ther someone out there to give me a clue?

    THX,

    tnt

  3. In several of my programs I use the name of a typedef as an identifier.

    Since LV 7, there's an option (which is default ON):

    "Disconnect type definitions and remove unused polmorphic VI instances"

    When building an application (as small as possible), I only want to choose

    for the removal of the unused polymorphic VI's

    but I DON'T want to disconnect my typedefs.

    So why is this one option in stead of two ...

  4. Hi Dave, you're not alone...

    Occasionally I've noticed the same behaviour on my Win2K-PC running LV6.1,

    especially when another process in the background was busy and causing a slower LV-startup,

    or opening several vi's at the same time.

    I'm also curious what others have to say about this...

  5. Hi,

    I prefer AutoIt v3 :thumbup: .

    When using their SciTe-editor you also have access to a form builder

    for fast and easy creation of simple GUI's.

    The best part is that it's freeware and it's very simple to create small executables

    (even with encryption to prevent decompilation).

    If you try it, I recommend installing the beta release because it also supports

    some nice things like a context menu for a trayicon... :star:

    http://http://www.autoitscript.com/autoit3/

    grtz,

    tnt

  6. Hi Martin,

    it's NOT very common to constantly initialize the COM-port, then sending a command and then closing the port again.

    It's better to do the initialization before your while loop, sending the commands and closing the connection when stopping the while loop (or add an initialize and a close button/event).

    I've often noticed a difference in behaviour (cleaning up memory) between running in Development mode and in Run-time,

    especially with serial (VISA) communication.

    I also advice you to handle possible VISA-errors in case something goes wrong (and showing the stop button?)...

    Good luck...

  7. Resize 2D array

    Inputs an array as Variants and outputs Variant Numeric String and Boolean arrays containing the original and expanded or contracted to the requested size.

    I would be interested in the comments of LV people as to whether this is a viable approach to polymorphism. The input array is converted to the output types at some considerable computational effort. However in a user interface situation programmer convenience (IMHO) greatly outweighs the time lost in execution.Download File:post-230-1133113101.zip

    hi,

    I guess you already know that you need LV Pro to create "real" polymorphic VI's

    and that this is a way to do something similar.

    This solutions seems to be rather memory-intensive, especially when using large arrays,

    because you create 4 different arrays out of 1 variant array.

    About your implementation:your performance/readability will improve if you would use

    the "Get TDEnum from Data" from the OpenG-toolkit. It just gives you the datatype of the variant.

    I haven't had the time yet to inspect what you are doing in the remove trailingzeros,

    but I know that when using a general expression like e.g. 0*$ and then removing the last point

    if the number appears to be an integer results in much more readable code.

    GrtZ, tnt

×
×
  • Create New...

Important Information

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