Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/07/2010 in all areas

  1. Show the Boolean Text of the checkbox instead of the Label. This will give you the behavior you're looking for. -D
    2 points
  2. shoneill (LAVA) = shoneill (NI) = Intaris (NI)
    1 point
  3. Try cmd /c ""C:\Program Files\OpenOffice.org 3\program\scalc.exe" "macro:///IES13148.Module1.PrintDocument(C:\Documents and Settings\test13.csv)"". My initial test was cmd /c ""c:\foo bar\hello.bat" bar baz" where hello.bat is simply @echo %1 and bar and baz are separate parameters. You can stick them together by putting them in quotes ("bar baz") but then the quotes are included in the output. You can nest quotes within those quotes without consequence ("foo "bar" baz") and the output is literal, even with a pair of double-quotes. You can actually drop the trailing quote for any of these parameters and it'll drop it in the output, but that's kind of taking advantage of the parser and you can't guarantee a particular outcome anymore. The ^ character is the escape character, but I couldn't get it to make any difference. This is all assuming your space in the path is going to mess things up, and that you'll need to encapsulate it in quotes, of course. There's an off-chance that OpenOffice would accept single quotes instead of double quotes to preserve the macro's parameter. Cop-out: is there any reason you can't use 8.3 filenames here?
    1 point
  4. Great, now we are starting to get better information. Here is version 2 The program will separate the high values from the low values. values above the threshold input will be considered high and below will be low. Only low values will be averaged high values will not be modified. Here is the graph of the original waveform And this is the new modified one. Try this out and let me know. Please give us as much detail as you can explaining any issues you still have Mark. LAVA Guidence MB help v2.zip
    1 point
  5. We are sounding out your possible interest in a new book that is in the works, called: LabVIEW: A Developer's Guide to Real-World Integration. We are contacting developers in hopes of gaining contributions that will make this a valuable text for LabVIEW integrators. We are in search of new material (previously unpublished) in the areas of hardware and software integration within the LabVIEW environment. If you have a library, utility, or application that falls within this area and would like to author a chapter, we would like to encourage you to contact me as soon as possible. Many Thanks,
    1 point
×
×
  • Create New...

Important Information

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