LabVIEW Idea Exchange

The title says it all: The property dialog of controls should allow inspecting and changing the default value.

Here's how it could look like.

Sometimes I wand to re-define a default value without actually changing the current value.

current steps

• copy the current value elsewhere
• enter the desired default value
• right-click...data operations...make current value default
• restore the original value (could lose data in case of DBL!)

After implementing the idea

• right-click...properties...enter default value...OK.

Hi all,

What I'm asking for is an optional indication of reentrancy in the context help window.

This would save the user from having to open VI Properties on several VIs, and would be particularly useful when viewing the VI hierarchy.

I realize that Greg Freeman suggested something similar.  My intent here is to narrow down several ideas from that conversation down to a single suggestion.

(I hope I still didn't manage to post a duplicate. Apologies if I did.)

Thanks,

Jim

Currently text in an "unbundle by name" node is centered. This makes for poor readability when there are several elements being unbundled.

I think that changing the justification from center to left does improve readability.

Note 01: This apply to bundle by name as well.

Note 02: implementing this idea my gave us this one for free.

I would be surprised if this is not a duplicate but I was unsuccessful finding it.

The subject says it all. Simply add a scrollbar to free text labels. I sometimes use a string constant for free labels simply because they can have a scrollbar.

The idea is quite simple to implement, I suppose.

Two main benefits:

1. allows you to know the exact size in pixels that the front panel will get at runtime, while the manual resizing of the FP occurs.
This feature should take in account VI's Windows Appearance options (Window has title bar, Show toolbar when running, ... etc). It helps you to set the FP size for the (different) screen on wich the program has to be run.

2. this feature can help you to set the BD size for the smaller screen on wich you know you'll have to edit the program.

Up to now you can only set a minimum FP size, and use it as a sort of "pixel size reference". However this is the internal net size of the panel, toolbars and title bar excluded, and the final setting is a bit tricky. You can also programmatically change the FP size, but this is of little use, if you don't want to risk that some control disappear out of the panel boundary.

The second benefit is only for those of you that use LV on different PC (Lab and laptop, for instance) like me...  and, like me, hate having to scroll the BD for editing it :-). Usually I set the BD size to the maximum possible dimensions of the smallest screen I use.

Cheers

Windows 10 now handles long file paths although it has to be enabled with via various possible registry or group policy edits. Windows applications have to opt in. LabVIEW source code should be able to utilize long file paths.