06-09-2022 10:00 AM
Morning folks,
When I first came across DQMH, I immediately liked those "double dash" suffixes as soon as I saw how much more readable they made a larger project. And I just wanted to share with everyone a new one I've started using that I really like.
When making my MHL cases for a new Request (ex. Modify Step.vi), I found that in general, space requirements dictate that I should just make SubVIs for most of those Requests that contain the actual code, as shown. To solve the namespacing issue, I started using the new double dash suffix "--sub" to indicate that, for example, "Modify Step--sub.vi" is the SubVI containing the actual code to handle the Request "Modify Step.vi".
Nothing fancy, but it gets the job done. Happy coding y'all 😁
Saying "Thanks that fixed it" or "Thanks that answers my question" and not giving a Kudo or Marked Solution, is like telling your waiter they did a great job and not leaving a tip. Please, tip your waiters.
06-09-2022 05:51 PM
Nice way to organise things. I like it.
06-18-2022 10:15 AM
Speaking of DQMH organization, I've noticed that standard virtual folders that I create, and later made part of a DQMH template, don't get created when I make a new module from the template. Is this the expected behavior or might there be something wrong with my template or DQMH installation?
06-20-2022 11:11 AM
Are you referring to virtual folders inside or outside the module library? The virtual folder organization within the template library should be unchanged when instantiating the template (because the .lvlib is just a saved copy of the template).
If you have a template library where this issue is reproducible please attach it to a reply along with specific steps to reproduce so I can investigate further.