Leaderboard

Hi Honey

Software design has many questions that need answering, and this is one of them. I've seen some software written where each dialog in the application was its own separate VI running a while loop in parallel with the other ones. Each VI and loop had a messaging scheme to show and hide the dialog. This mean there were something like 10 parallel while loops just handling dialogs. This goes too far. I've also seen applications that have one while loop, where DAQ data logging, report generation, sequencing, communication, database control, and UI were all in a single loop. This didn't go far enough. In the end it is up to you to decide how it should be designed, and personally I don't mind adding parallel loops as long as the functionality and responsibility of the loop is well defined, and encapsulated. Performance-wise it might become a problem. An atom is not a powerful PC, and if each loop is doing lots of work in timeout cases you will have a problem eventually. But if most of the time, most of the loops are truly idle, not polling anything, then I wouldn't worry too much about it.