Jump to content

Zou

Members
  • Content Count

    57
  • Joined

  • Last visited

  • Days Won

    4

Zou last won the day on March 13 2018

Zou had the most liked content!

Community Reputation

13

About Zou

  • Rank
    Very Active

Profile Information

  • Gender
    Male
  • Location
    Dallas, Texas

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2014
  • Since
    1990

Recent Profile Visitors

1,362 profile views
  1. You can add an animated GIF as a decor to a button, just like other image types. See attached ctrl.AnimatedGIF.ctl
  2. Put a transparent decor on the numeric control, partially block the button, so that user can only click the up/down button.
  3. 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.
  4. 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.
  5. Is there a way to prevent this ? Or should I check every ctrl ?
  6. 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
  7. I got the same message from NI about the LabVIEW SoftMotion Module. We just switched from FlexMotion to SoftMotion this year !
  8. Version 1.1.0 overwrites the .ini settings.
  9. Can't you use property node=>Path Text=>Scroll Position instead?
  10. > 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.
  11. Sounds like a font problem. Don't use application font, or dialog font, ... choose a specific font, for example: Segoe UI
  12. 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.
×
×
  • Create New...

Important Information

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