Flat sequence bug

[UFOslava]

No bad feelings on slight derail, its amazing how people are willing to help 🙂

Code salvaged and rewritten. This is a report part of a large project, made to manage tests with explosives. After disaccembling the code, 35 new VIs were created. Now it contains 336 files.

Back to topic, there was no mention of any limitations in the block diagram length in any lab-view books i came across.
I found it very easy to develop just 1 large vi as i use 2 screens and use "crawl" tool (ctrl+shift). Whole code was flattened in front of me and it was easy to navigate. This particular vi grown beyond imaginable because of the modularity and count of options on the front panel. It's required to be ready for any plots and few simple checks of pass/fail on them. Event was supposed to handle all user requests and deliver the final xls file.
I saw no other way to complete the task.

[Mark_Yedinak]

---

@UFOslava wrote:

Back to topic, there was no mention of any limitations in the block diagram length in any lab-view books i came across.
I found it very easy to develop just 1 large vi as i use 2 screens and use "crawl" tool (ctrl+shift). Whole code was flattened in front of me and it was easy to navigate. This particular vi grown beyond imaginable because of the modularity and count of options on the front panel. It's required to be ready for any plots and few simple checks of pass/fail on them. Event was supposed to handle all user requests and deliver the final xls file.
I saw no other way to complete the task.

---

That is the beauty of regularly reading the forums. You get exposed to better techniques, designs and architectures which will improve your code significantly. Also, a very good lesson to learn is that taking the simplest and easiest approach is not always the best thing to do in the long run. I always keep maintainability and feature enhancements in mind when I develop code. What may look like unnecessary complexity in a simple program will turn out to be your saving grace when changes are required. A flat sequence with lots of frames may seem like the best solution because it is fast and easy will byte you in the butt because it starts to become impossible to modify or add features later on. Rarely have I ever written something and never touched it again.

Thanks for quoting me in your signature. You should add "the diagram is way too big" to finish the thought. 😄 Anyway I feel honored to make it to a person's signature.

[billko]

---

@UFOslava wrote:
No bad feelings on slight derail, its amazing how people are willing to help 🙂

Code salvaged and rewritten. This is a report part of a large project, made to manage tests with explosives. After disaccembling the code, 35 new VIs were created. Now it contains 336 files.

Back to topic, there was no mention of any limitations in the block diagram length in any lab-view books i came across.
I found it very easy to develop just 1 large vi as i use 2 screens and use "crawl" tool (ctrl+shift). Whole code was flattened in front of me and it was easy to navigate. This particular vi grown beyond imaginable because of the modularity and count of options on the front panel. It's required to be ready for any plots and few simple checks of pass/fail on them. Event was supposed to handle all user requests and deliver the final xls file.
I saw no other way to complete the task.

---

Whew!  Glad you were able to piece it back together.  I think you're definitely on the right track now.  Sub-VIs in the main BD are the way to go.  🙂

[UFOslava]

We dont have internet access here, so i can only dwell here at weekends 😕

Also, i am known in my team for building ridiculously large block diagrams. That's why the quote went along 😛

Thanks to everybody!

[Mark_Yedinak]

---

UFOslava wrote:

Also, i am known in my team for building ridiculously large block diagrams. That's why the quote went along 😛

Thanks to everybody!

---

Not to belabor the point but this would be a good habit to break. It will make both your life and your coworkers life much easier.

[JÞB]

Glad you are back on track!  And, I too am honored by the signature line quote.  I think its a first for me