LabVIEW Idea Exchange

It would be nice that if a VI documentation set is created into HTML with PNG as picture format a snippet option would be included.

This option would embed a VI snippet of the top-level BD inside the PNG instead of a static image.

This way it's possible to distribute the code inisde the documentation.

 

 

 

The VI>Properties>Vi documentation could use an overhaul.  Simpler access from the Menu (A ribbon button ?) Templates and Auto insertion of definable fields.  A real text editor launch and well how about being able to resize the edit box so you can see what you typed.   Cut-and Paste from notepad works - but can't we get a bit more elegant than that.  Type bold text - get Bold text Underline, italics.  Justify left center or right.  Heck- this editor for the Idea exchange would look great in my vi documentation pop-up.

One of the quickest (and easiest to forget) methods to improve performance of your VI is to disable debugging.  It requires a trip down the VI properties to get there, however.  I propose adding a button on the BD alongside the other debugging buttons to Disable and Enable Debugging.  

I need to detect when a user has released mouse control of a slider, but that is not possible. I would like to see a new event on controls called "User Control Ended".

 

For instance, consider a user grabbing a slider knob:

 

 

The user is able to drag the mouse anywhere, even outside the bounds of the window, and still have control of the slider:

 

 

And if the user Mouse Ups outside the window, you can't detect when that event happened. Here, Mouse Up and Mouse Leave are of no use on either the control or the pane. The new "User Control Ended" event needs to be robust like "Drag Ended", detecting events that happen even outside the VI pane.

 

Conclusion: when a user is interacting with controls using a drag-like operation, I need to know when the user releases the mouse button, whether it be inside the pane, outside, wherever. I have illustrated the example using a slider, but the idea I think should encompass nearly all controls (e.g., a user clicks on a Boolean with "Switch when Released" mechanical action, then drags the mouse outside the Boolean and releases to effectively cancel the Value Change event. Well, I'd still like to catch the "changed mind and released mouse button elsewhere event", a.k.a. the "User Control Ended" event)

 

 

EDIT: Attached the VI so you can play with it.

It would be absolutely helpfull if Graphs would have Annotation font properties like Labels  have on generic control.

 

 

New properties for Annotation in annotation List that could allow to change "test" text fonts attribute.

 

 

Microsoft introduced a number of restrictions in Vista that makes it more difficult to save program settings and temporary files.

 

Applications can no longer write to the Program Files directory, but even worse; the common application data directories, like ProgramData and Users\Default  are by default only accessible for writes by administrators and the first user that did the write. Sessions by other users only have read access. The same goes for registry access; the computer keys can not be written by everyone.

 

As long as it is OK to not share settings between user's you have one good option left; the user's appdata folder. If you do need to share data though - you need to set the access right of the folders you create in the "common" directories. This can currently be achieved e.g. by using a tool like SetACL, however as it has been made a required action now, it should be included in the installer - AND preferably also as VIs on the file and registry (for registry access) palettes.

 

LabVIEW 2009 introduced one of the tools required to handle the UAC changes - a VI to get the paths of system folders. It should also have a tool to grant access to some of those paths...