Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Zou last won the day on March 13 2018

Zou had the most liked content!

Community Reputation


About Zou

  • Rank
    Very Active

Profile Information

  • Gender
  • Location
    Dallas, Texas

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2014
  • Since

Recent Profile Visitors

1,227 profile views
  1. Version 1.1.0 overwrites the .ini settings.
  2. Can't you use property node=>Path Text=>Scroll Position instead?
  3. > I do use application font but I was hoping not having to go through thousands of VIs to change their font setting. But it seems that's the only Do it programmatically. Here is what I would do: Change LabVIEW font option to Segoe UI or any specific font, make it panel default. Programmatically open each VI, and simulate a Ctrl-A to select all, then simulate a Ctrl-4 to set font to Current Font. Save the VI.
  4. Sounds like a font problem. Don't use application font, or dialog font, ... choose a specific font, for example: Segoe UI
  5. Because LabVIEW doesn't use Windows objects, so LabVIEW controls have no object ID. Only LabVIEW knows where the controls are. To OS & other applications, there is nothing on the front panel. Only 2 exceptions: ActiveX & .Net containers. The containers are child windows. Therefore they should have an object ID.
  6. Thanks for reply. We don't have a fixed distance. Currently, autofocus is the only problem we have. Our target is as large as an engine. No image process. Just save to file for record.
  7. I'm looking for a color camera with built-in auto-focus feature. Please help. George
  8. Thanks for the quick response. The exe uses a 3rd party HW and SDK. The SDK, once called, left something in the memory. I can't get rid of it. And I can't run it the 2nd times until restart LabVIEW. So I've to put it in a separate process.
  9. I can get VI refnum and set/get control values, but I can't find any method to trigger a button click event or any value change even. Anyone did this before?
  10. That's because NI takes care of the cross platform issue. The source code for LabVIEW itself is implemented depending on OS. For those features LabVIEW doesn't support (yet), you can implement them yourself.
  11. LabVIEW objects are not Windows object, so you can't create LabVIEW ctrls dynamically. However, you CAN create Windows objects (e.g. text box, for both numeric ctrl & string, picture box for images, and static obj for decor. etc.) on the FP dynamically with or without a container (a child window if no container). Animations, skins, drag & drop, etc. all can be done with Windows API, just like other programming languages (e.g. C#, VB) do.
  • Create New...

Important Information

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