Tabs or Sheets like Microsoft Excel

[Chris_in_Colorado]

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!!!!!!!!

[crelf]

Do you mean something like a stacked sequence structure, but with a better way to select which page is showing?

[RavensFan]

Chris,

I'll post here hoping you have a subscription turned on to your own thread and see this.

There is no need to post meaningless comments in every message idea where you like the idea.  That is what the Kudoes button is for.  If you have something meaningful to add, like another interperation, a variation of the idea, a reason why you don't like a particular idea or think it shouldn't be, then go ahead and post a comment.

No need to create a comment that just says "I like it!"  It just clutters the Idea board, and also fills up my inbox

[Chris_in_Colorado]

The problem with a stacked structure, is that if one section is huge, all of them float in a huge box.

No, tabs at the top or bottom, LIKE MICROSOFT EXCEL. 

in excel you can call "=sheet3:A1 + sheet2:B7"

All data and forumulas in one EXCEL workbook, but spread over many sheets, each cleaned up

Raven is verbally abusive. What a rant.

[RavensFan]

What part of my message is abusive?

Yes it is a rant because I don't want to see one person, let alone dozens of people post "I like it" in every single idea thread without contributing something meaningful to the thread.  As I said, those kinds of comments just clutter the boards as noise.

Did you even realize what the Kudoes button is for?  I don't think you did because the messages where you posted "I like it", I have yet to see one where you kudoed the idea.  I am hoping to educate you a bit here.

Think about those most popular ideas where over 100 people kudoed the idea.  Do you really want to sort through over 10 pages of "yeah"  "Good Idea"  "way to go" to find the meaningful comments where people may evolve the idea, discuss the pros and cons?

I sure don't.

[smercurio_fc]

I know, let's ditch LabVIEW alltogether and program in VBA. Then it will be really like Excel.

I'm guessing you'll probably like this idea as well: Vertical Stacked Sequence.

P.S. In case it's not obvious, I'm being satirical. 

Putting on my serious hat: Seriously, what benefit does this idea have? You're (a) hiding code, just like a sequence structure, and (b) advocating the use of local variables. Both of these are exactly what you should avoid in LabVIEW programming. 

[JackDunaway]

Chris - Tell us how you would not have the overhead of many subVI's. I agree with the other's comments, but if there is a way to eliminate subVI overhead, I'm willing to listen. Regards, Jack

[Intaris]

I htink this idea meant that the individual "sheets" would all execute concurrently.  Just a way to split up independent parts of the main program BD if I'm not mistaken.

I remember working on a 5-axis robot which we had bought second-hand where the controller was written in a  language called LUCIE and it too had 8 "independent" portions to the code (which ran semi-concurrently).  It was an interesting idea but I don't see how splitting up a BD like this would be a benefit over having parts in sub-VIs.

Somehow I'm not sure how this would work out. There'd need to be some easy way of communicating from sheet to sheet to make it even viable and this would almost cetainly have to be an asynchronous communication.  In a way, a producer / consumer architecture with seperate parts of the BD for each part could have its appeal.  Due to the effort which would be required for this implementation and the wealth of other things I'd like NI to do, I'm not voting for this one.

[G-Money]

This would make code harder to read and communicating with local variables should be limited because they break the data flow paradigm.