Zou

那不正是 Hu 做的吗？问题是边框的颜色不是单一的。

WebRing is down. I moved the page to GitHub: GitHub - Zou-LV1990/PropertyPages: Customize LabVIEW Property Pages

If you can't get ActiveX to work, you can always use Windows API. https://forums.ni.com/t5/LabVIEW/How-to-run-an-exe-as-a-window-inside-a-VI/m-p/4096356

That's not accurate. It's more like this: - All states looks different decor: 1 decor, - True state has decor, False state has no decor: 1 decor, - All states looks same decor: as many as you want. 2 decors.ctl

Thanks. But there are many other components you can "Steal" from NI ctrls. For example, the 3-D semi-circles from the Modern thermometer ctrl. In addition to replace an existing component, you can add extra components to a ctrl as long as you can set the component to be slave of the housing/frame. Untitled 2.vi

Could you save it to LabVIEW 2018? Thanks.

You can get a semi-circle from the Classic Tank.

You need the .h file which defines g_hSystem.

Right click a glyph and copy it to clipboard. Then you can import the image as Decal. boolean glyph.ctl

You can import boolean glyph as Decal to any button. For other controls, you can add images as long as you can set it to "slave to frame". Only LabVIEW decorations (vector image) can resize without problem. There is no way to change a 4 part items button to 6 part items button.

You can also configure the exe (or it's shortcut) to "Run this program as an administrator" on the file properties dialog window in the Windows Explorer. One way to verify if the LabVIEW is run as admin is: the path ctrl doesn't works with drag & drop.

Button outside the window:

Demo VI attached.Search Unicode String.vi

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

Saved in LabVIEW 7.1. Run Application.vi

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.

Use the NI Tool. One property node is not enough.

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

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.

You can add an animated GIF as a decor to a button, just like other image types. See attached ctrl.AnimatedGIF.ctl

Put a transparent decor on the numeric control, partially block the button, so that user can only click the up/down button.

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.

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.

Is there a way to prevent this ? Or should I check every ctrl ?

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