I've read the one book/gospel on LabVIEW style and read plenty on various blogs and this forum about how nearly everything needs to be in its own little subvi and such. But I'm here to say it's a little bit too much. I understand it's nice to have code that fits on the screen, and I agree, BUT... we're not talking about 1024x768 CRT monitors anymore and if I have to bundle + un-bundle a cluster with descriptive labels (as has been drilled into me) there is just no room whatsoever to do that or anything more. It feels constraining, it feels like a holdover from the days of yore, and it just doesn't make sense to me that there isn't just a bit more room to work (like my dad wants me to use an ox to plow a field b/c that's how he learned it). I know I can ctrl-drag myself into some elbow room/freedom but it just makes every other frame/case messy. So how about it Delacor? Be the new trend setter, give the people what they want, set them free! Or at least provide a few more inches of leg room. Make it the default in the DQMH tools that are already awesome. I have the same critique for the JKI state machine (though it is more roomy than the DQMH MHL), which I also love. There's just hardly any room to do anything, I'm not talking about a bunch of space for me to make spaghetti, I'm just talking about enough room to have descriptive labels, code documentation, a few subvis maybe, whatever... All of which will happily fit on my not-at-all-modern, not big, employer supplied monitor with plenty of real estate to spare.
I can't tell you the number of times I've agonized over whether I wanted a helper loop (or just went ahead and made one), when it was really just a tiny bit more MHL room I needed and a helper loop was really unnecessary. I think there are lots of other "coding conventions" that need a fresh, two-decades-into-the-21st-century, re-examination.
I mean this in the nicest way possible, I highly admire DQMH and the especially the support offered along with it.