LabVIEW Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

Wow,

 

This would be super powerful.

 

It's a little hard to grasp at first.

 

If you have sheets or tabs like EXCEL, you could write clean code in small chunks without have all the overhead of many SUBVIs!!!!!

 

I would use "local variables" to get data back and forth from different tabs/sheets.

 

TAKE 1 MINUTE TO THINK ABOUT!!!!!!!!

 

I've had case statements with 50 items.

 

It needs better tools

 

1. Delete cases in popup

 

2. Rearrange more than one case in the popup before it closes

In text based language, define some constants with meaningful names are very common task. For example, you typically define constant in C like this: 

 

#define RED          1

#define GREEN      2

#define BLUE         3

 

In LabVIEW, you can use ring to define them: 

color ring.PNG 

 

and then you can use the constant very simple: 

 use color ring.PNG

 

But the following definition can not be implemented with ring:

#define RED          1

#define GREEN      2

#define BLUE         3

#define DEFAULT   1

Here, DEFAULT is the same with RED.  But this is not permitted by ring, it will popup a warning if you try to do this: "Waring: Identical values in the Values list are not permitted. The oblject cannot be updated until you assign new values or remove items with identical values. "

 

I know you can use local or global varibles to define constant as a work around, but variables have performance overhead, it is not the best solution as a result. 

 

I propose to create a "const" that allow different items share the same value, and the other behaviours will be the same as a ring. You can also add "picture const" and "text & picture const". 

 constant.PNG

 

The following topic on NI discussion forums inspires me to propose this idea.  

 http://forums.ni.com/ni/board/message?board.id=170&thread.id=435687

 

It would be very useful to have a way of automatically create subvis when a single vi become too large. What we usually do is :

1. Select the portion we want ton encapsulate in a new vi.

2. ctrl-X.

3. Create new VI, save as, chose name, change icon.

4. ctrl-V.

5. Connect the front panel.

6. Add the new vi to the original diagram.

7. Connect the new vi.

8. Debug mistakes.

 

I think steps 2 to 8 could be automated with a single function (e.g. 'transmute selected code into a single vi'), saving a little time many times.

A conditional terminal for each frame of a sequence structure would allow one to exit the sequnce at any frame.  This could be useful in case something occured in one frame that meant the remaining frames should not be executed.  Easier than having to use case statements in the later frames.

 

I'd like to have a user dialog that shows a message to the user but doesn't wait for the OK button being pressed to continue. I want to use it as a simple informative pop-up window that the user can close whenever he or she read it, without my code having to wait for the OK button.

I now use a self made VI that I call using the VI Server method 'Run VI' with 'Wait until done' set to FALSE. Or did I miss something obvious?

 

Manu

Sorry if this is a duplicate.  I though I posted this a couple of days ago, but it hasn't appeared.

 

 

These are suggestions for this site:

 

Add a label: "Ideas Exchange Enhancements"

 

Put "Previous" and "Next" at the top of the page as well as the bottom.  Better yet allow us to go to the first, last, or particular pages like other forums (ex:   << 1 2 3... >>).  Put this interface at top and bottom.

 

In advanced search give the option to go to the PAGE the idea appears on rather than the idea itself.  Currently if I search for a particular date (the last time I looked at ideas) I get a list of ideas for that date.  If I click on an idea I go to the idea itself and any posted comments.  There doesn't seem to be a way to get to that day's page of ideas short of starting at the first and clicking on "Next" over and over.

 

Add a modifier key when we close one probe (CTRL for example) will close every probe.