Jump to content

crelf

Members
  • Posts

    5,754
  • Joined

  • Last visited

  • Days Won

    54

Posts posted by crelf

  1. 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.

  2. 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!

  3. 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).

  4. 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.