Jump to content

crelf

Members
  • Posts

    5,759
  • Joined

  • Last visited

  • Days Won

    55

Posts posted by crelf

  1. I know that I'm coming in really late on this, but my background image is obviously a programmer's - it's not very imaginative, but it sure is functional:

    post-181-1141482229.jpg?width=400

    Note: if you're going to use it, ake sure you remeber to set it a "center", and not "stretch" ;)

  2. But when "A" (running as a standalone application) tries to start "B" (also running as a standalone application) then "B" will open up broken.

    Thanks for the explination - I agree: I've had the same issue in the past, but the problem that I'm currently having happens in the development environment - I haven't even tried it as a built exe yet :)

    To use the Run method, don't input a type specifier when you open the reference. You need a type specifier only for calling the VI with the invoke node.

    I know that I I don't need to use a specifier to just run a VI dynamically, but I'm using it this way so the error cluster allows me to determine if the opened VI is of the correct type to use as a plug in.

  3. ...you can still monitor the mouse movements using the Mouse Device VIs and figure which item is highlighted.

    I'd thought of that, but it's not as trivial as it sounds. I'd need to take several things into account:

    * font size, as you mentioned

    * what item was selected before the user clicked on the control (this determines where the new 'window' pops up)

    * screen resolution and position of control relative to the top / bottom of the screen - this also determines where the 'window' pops up.

    :lightbulb: Maybe I could do it using relative move movements...

  4. Hey all,

    I'm using VI server to load and run a VI dynamically, but I'm getting:

    Error 1000 occurred at Invoke Node in Start Threads.vi

    The VI is not in a state compatible with this operation

    I know the VI is fine (it's not reserved for executiong, I can run it manually, and it's idle when I try to call it).

    post-181-1141422493.gif?width=400

    Note the image over the title of the type specifier - I wonder if this is trying to tell me something?

    Anyway - see the attached files: unzip the zip file to a new folder and point the path control of LittleBugger.vi to that new folder - I can't understand why the Motion (Linear) Thread.vi won't run...

    Download File:post-181-1141424835.vi

    Download File:post-181-1141424750.zip

  5. Use the "Format into String" primative (it's under the "string" sub-palette of the functions palette), and set your "format string" to %04d - the % is the format sepcifier, the 04 means use a minimum field width of 4 characters, and the d tells the function to format is as an integer.

  6. Hi All,

    I'm putting together an update to the OpenG custom user interface toolbar buttons (partly because I have a bunch to share, and also because I want to learn more about contributing to OpenG). If you've got custom buttons that you use on your UI, please submit them to be included in the package to share for the greater good of the LabVIEW community! Below is a graphic of the buttons that have alread been submitted:

    post-181-1140733469.gif?width=400

    If you've got others, I'd love to hear from you!

  7. To parse your input string, why not split the string at the "space" and handle the two parts separately?

    Personally, I'd definately go with Jim's method - the "unit" of data is a very underused feature of LabVIEW, and (as Jim says) as long as you keep your units consistant, it takes care of itself (eg: wiring a control in meters and a control in seconds to a divide primative will yeild a solution in m/s - if you wire that to an indicator with units other than m/s will give you a broken arrow).

  8. Has anyone used the splitter bars in LV 8?

    I love it - It's really easy to create quasi-toolbars (you can pick the toolbar up and move it around, or dock it anywhere else, but for a static toolbar, it's pretty neat!

    I use a bunch of custom Booleans for toolbar buttons that I put together *years* ago - I hope to put them up on OpenG very very soon:

    post-181-1140031639.gif?width=400

×
×
  • Create New...

Important Information

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