LabVIEW Idea Exchange

Is LabVIEW available for Android based systems and other touch interface systems.If not how about using LabVIEW for mobile measurements using these systems.

It would help a lot if we have an option called pause on first Error. So that the VI at the node/primitive that generates the error and highlights that node so that user decides to continue or abort.

Have you ever created a cluster like this?

I have. Numerous times. It's fairly easy to create clusters which get out of hand. The magic number is usually around 10-15 elements, assuming some of them are clusters as well, but even if those numbers are manageable, I've also created larger ones, and those aren't manageable.

Using LVOOP mitigates this to some degree, but does not solve it completely.

So, it would be great if we could divide the cluster into "pages" or "categories":

This will allow us to logically divide the cluster into manageable areas.

The names of the pages will appear in the selection list and in the unbundle node, as shown in the example (although you could hide them in the node by unchecking the full names option), but they will NOT actually be part of the element's name. Changing the name of a page or moving an element from page to page will NOT require you to change code which already uses that element.

Notes -

1. In my mockup I used a tab control. I understand that LV R&D has some aversion to the concept of tabs inside clusters, so I would like to make it clear that I'm NOT asking for a tab inside a cluster. This is purely a cosmetic and organizational feature.
2. I already posted this as a comment on this idea, but I figured it was worth posting as a separate one.

String containers have display format Glyphs to help us understand the String Values when the display is Normal, Hex or Escape codes.

Integer numeric type containers have them too to show radix.

Timestamp containers must be inspected for their display format property to determine if they are in System Time or UTC.   

Timestamp Controls, Indicators and Contsants SHOULD have a similar optional display format glyph.

This could be used instead of the misleading coercion dots when operations are performed on Timestamps as Seen Here 

Estimate and show the Time Remaining during LabVIEW Installs, using selectable and realistic time units:

.

It's useful that we can open the Error List window via the Ctrl + L shortcut.

It would be great to have keyboard shortcuts that allowed us to navigate to the next and previous errors (broken run arrow locations). This would be similar to how Ctrl + G and Ctrl + Shift + G can be used to navigate to the next and previous result in the Search Results window.

I would be happy with any key combinations chosen for this purpose.

Thanks

I would like to be able to change the z-order of FP Objects programmatically. For starters, I envision the following properties:

1. Layer - Explicitly sets the z-order layer in which an object resides.
2. Promote/Demote - Implicitly sets z-order layer by -1 or +1 (assuming Layer 0 is frontmost)
3. Send to Back/Send to Front - Explicitly sets z-order to the foremost or rearmost layer
4. (Optional) Container property "Layers" - Returns an array of all layer indices currently in use by the container (Page, Panel, Cluster, etc.)
5. (Optional) Container method "Layer.Objects" - Returns array of references to all objects on a layer

I'm totally on board with Embedding Labels for Property and Invoke Nodes! Here are some additional improvements to those nodes:

Property Node Concepts

Scripting and Invoke Node Concepts

1. Most importantly, the banner now more closely resembles a Static Control Reference.
2. The directionality arrows are a pixel width's larger - more distinct, and matching the size of the new LV2010 Local Variables.
3. The node banner is the same height as the unlinked property node.
4. Property Nodes and Invoke Nodes are distinguished by the Property Wrench and the Action Arrow glyph.
5. Scripting properties/methods are now more distinct. Currently, the small node banner inherits a few pixels of light blue distinction if any one property on the property stack IsAScriptingProperty. Proposed, shading will be applied on a per-property basis, allowing better visual distinction and a more coherent choice for what to shade.

Discussions/suggestions/insults/questions encouraged in comments section!

Why not create the option to change how the data is viewed on screen, similar to formatting in Excel or the Calculator function?

This could also be used for a hex display (I.E. FFFF FFFF), octal or even binary.  Options could be expanded to include how many characters before separation and what to use as a separator.