It would be great to have possibility to change/edit the code when a VI is running in "Suspend when called mode".
This would be a code developer ultimate dream when you are into development of new code or just fault finding in old code.
During development or fault finding when/if you are using "suspend when called"-functionallity for a sub VI in your code.
I mean when the sub VI is "paused" and waiting for you to press the "run" button, right there, possibility to edit the code for that VI and run it ones, change the code (perhraps changing some timing or changing a formula of an calculation or both or change execution order for some settings of the DUT etc etc) a little bit and run it again, tweak it a little bit more and run it again... AND THEN exit the sub VI (with "suspend when called") and CONTINUE with the rest of the CODE like nothing have changed!
A kind of possibility to change the code during execution, just for VI/s that you have chosen "suspend when called" for.
What a functionality when you are into fault finding and testing out of new developed code! ! ! !
I think that this functionallity would make a big difference between text-based coding and using LabVIEW in matter of how easy development or fault finding can be done.
As in the subject.
Now when you create an array the indexes of the array can be only labeled as the static comment field. There is not any build-in label/handler which could be used. Current situation looks like that:
It would be better for readibility if developers could name the indexes and use it later on.
Picture represents the idea only, whole point is the description shoud be a build in handlers.
Now LV names first four indexes (when you hover over on it) as column, row, page, vol; later on are only dim 5, dim 6 and so on.
I believe if would increase readibility and save coding and debugging time.
Right now the Labview interface for arduino is available but it is only facilitating us to communicate to the board's i/o pins through Labview, better would be if we can code using Labview and run the code on the arduino board. In that way we would be able to process faster as compared to running code on the pc plus people not aware of coding can also play along using this stuff.
When dragging a control / indicator label or caption, if you move within a certain distance from the owning terminal the label will snap to one of a set of given positions (top-left, top-middle etc). Outside this distance (or if the user presses the spacebar to toggle this behaviour), the label can be freely positioned.
The selector terminal for a polymorphic VI should display the same behaviour with regard to the owning VI icon. A polymorphic selector is currently always free-floating.
PS : Many thanks to Intaris and TiTou for their help to formulate this idea.
I am not sure whether anyone had posted this requirement before, but I would like to have a Zoom In- Zoom Out functionality in LabVIEW.
Some times when code becomes too crowded its difficult to analyse which wire is going where.
Would be nice if NI would concentrate on fixing long standing bugs instead of creating new features dreamed by marketing...
There are threads in the forum about bugs that have been going on for 4-5 years! Ouch! They are there and it is not an excuse to say "we can't reproduce". Some bugs (intermittent or the type "we can't reproduce", have to be fixed by analysis, not by single stepping through the code. If one can't reproduce in the "clean lab" environment, analysis of the existing code is needed to find what could be causing the problem by the Customers.
We all experience them, don't we? So they are out there...
I find myself constantly switching between Quick Drop and palette surfing for the functions I need. Sometimes I close the palettes just because they are in the way of where I want to drop a function. But I immediately need to reopen them to find my next function.
Can there be a setting in the palette options to hide or minimize the palete once I've selected a function from the control/function palette and once I've placed the item on my front panel/block diagram it will reopen to the same palette and spot?
Say I've dropped two 2D array controls on my block diagram, and would like to change both of their appearances in the same way. I can select each one at a time, right click and head to Visible Items > Index Display. However, it would be nice to be able to select multiple items of the same type and have the option of applying the same change to all of them.
Currently, selecting both and right clicking lets me change the following:
It would be nice if LV could recognise that I've selected two identical controls and offer me the option of changing the display settings for each of them:
Expanding this, you could use the same approach for BD constants, such as setting multiple string constants to '\' code display, or disabling size to text.
The NI Volume License Manager has a tool to create a volume license installer.
If you want to include Drivers you have to copy them to the installer folder _src\DriverDVD and then modify the nisuite.xml file (depending on license server you run)
There needs to be a simple way to say add NI disc to installer folder. Or at the end of creating the installer it could ask if you want to include other discs.
This should work for adding the driver disc and other extras like the Xilinx Compilation Tools, etc...
That way you can easily put together a full LabView Development install location for users.
I was searching for occurences of a reference to a Graph in one VI, and as I was interrupted, came back to the search result after the interruption, only to discover that the Search Result Window did actually not show ANY kind of useful information regarding the object I was searching references for:
I know I have outrageous expectations as a LabVIEW user, but this seems to me an odd lack of feature:
- From this window, I have absolutely no clue what I am searching for. In particular, if I have in the mean time jumped from windows to windows...
- ...there is no way to go back to the object these references are linked to (unless I go to one of the references and then look for the Control or Indicator they are associated with).
Of course asking for a VI information when this is provided in the list below is maybe unnecessary.
But consider this global variable whose references I was looking for:
Same thing here:
- I do not know the type of the global.
- I do not know which VI it is part of (Globals are saved in a VI).
- I do not know where I started my seach from (but that's more of a back-to-source button issue).
Suggestion: provide as much information as possible about the starting point of the search, when said starting point is an object (by contrast to a text search).
Tested in LV 2013 SP1 64 bits.
Since Windows Seven, the system exec vi is not displaying accents but other ascii caracters. Depending on the Windows language I suppose.
This issue has been discussed since 2010 in different threads, manly this one : http://forums.ni.com/t5/Discussions-au-sujet-des-a
and nothing has changed.
Please add this to you next SP
Sometimes special characters like oC, greek letters or subsripts/superscripts are needed for controls, graphs etc.. LV doesn't seem to have much improved on this over the last decades (I haven't checked LV 2014). The usual workaround is to copy the needed characters from other programs. This procedure is cumbersome. It would be nice if future versions of LV included such a basic feature.
If this is done, some bugs could be eliminated on the way. The portability of characters between different OS versions (i.e. Englich W7 and Korean W7) has also potential for improvement.
this is NOT a duplicate of this one.
But I couldn't find a duplicate within a few minutes.
I'd like to have an indicator which shows if the case structure compares strings case sensitive or case insensitive: