Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Zou last won the day on March 13 2020

Zou had the most liked content!

Profile Information

  • Gender
  • Location
    Dallas, Texas

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2014
  • Since

Recent Profile Visitors

2,404 profile views

Zou's Achievements


Newbie (1/14)

  • Dedicated Rare
  • Reacting Well Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. Button outside the window:
  2. Demo VI attached.Search Unicode String.vi
  3. It's the "space" character problem. Build your own search function: 1. Change your unicode string display mode to Hex to find out the "space" character in Hex 2. Use it to convert your string to an array using the spreadsheet to array function 3. Use search 1D array to find matching word
  4. Saved in LabVIEW 7.1. Run Application.vi
  5. When a window (any window, including LabVIEW) is maximized on monitor1 (1920x1080), the window rectangle is (-8,-8,1928,1048) on my laptop (Win7 Pro). That extra 8 pixels on each side is the frame edge. I noticed this when I started to use Win7.
  6. Use the NI Tool. One property node is not enough.
  7. I did an English/Russian project last year based on NI Unicode tool: https://forums.ni.com/t5/Reference-Design-Content/LabVIEW-Unicode-Programming-Tools/ta-p/3493021?profile.language=en
  8. LabVIEW ctrls DO cause problem sometime. See my post: It seems LabVIEW has problem with translucent images occasionally. Even if the image is copied from the Silver Button.
  9. You can add an animated GIF as a decor to a button, just like other image types. See attached ctrl.AnimatedGIF.ctl
  10. Put a transparent decor on the numeric control, partially block the button, so that user can only click the up/down button.
  11. Use .Net OpenFileDialog (or Windows API GetOpenFileName) where you can specify the owner window. The dialog window will be in the front of its owner window.
  12. I added this gauge to an existing VI/proj. in LabVIEW 2014 SP1, and then customized it. The VI/proj. was upgraded from LabVIEW 2011 previously. Had a huge performance problem with a translucent button before, so I checked when I have performance issue again.
  13. Is there a way to prevent this ? Or should I check every ctrl ?
  14. It's getting and process redraw message like crazy ! Anyone had this kind of problem before? LabVIEW 2014 SP1, Windows 7 Pro. 64 bit. Tested with LabVIEW 2018 too. Control1.ctl
  15. I got the same message from NI about the LabVIEW SoftMotion Module. We just switched from FlexMotion to SoftMotion this year !
  • Create New...

Important Information

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