What is you most reused VI you came up with?

[paul_cardinale]

---

@VitSlaby wrote:

I'll add two VIs that I like to use for timing slow tasks in faster loops. For example there is a task in one of my projects where I check for free disk space every 10 minutes and if there is too little, I move files to sd card or delete them. But I also need the same loop to report to watchdog loop every 5 seconds. And once the app is set to exit, I want the loop to stop in a matter of seconds. This timer does the timing thing. There is a standard and autoreset variant.

---

Why so messy?  Here's your Timer Resettable.vi as it should be:

 

[JÞB]

I have my own Delay.vi any forum search will turn up. But I do tend towards Stall Dataflow.vim for cases where the exactness of Delay.vi is overkill or, transporting to clients without my reuse library. i.e. Forum use.

Time to XL.vi from here has the record for most marked solutions of any vi on the Forums! despite its travel restrictions. 

Here.vi (a codeless vi with an attention glyph icon I kept in vi.lib) was used for every code review until the hotkey shift+3 was available for free labels. Now retired from use.

My current most used items are vit and ctt TEMPLATES I keep in Frameworks and seldom use File New VI anymore preferring File New... and launching the template browser (MyCustom HOTKEY = Ctrl+N which ships creating a blank VI) Creating from Template adds base documentation and Icon starting points.

[JÞB]

---

@raphschru wrote:

 - My own implementation of "Split String" to manage more corner cases like no separator in the input string, empty last element or empty regex:

 - A simple and compact error inserter:

---

You want to right-click that Merge Errors and select "Retain all errors" it changes the glyph so, I know you missed that additional option in 2020.

[Henrik_Volkers]

One I very often resuse is for changing the name of a wfrm to feed a (usually mixed signal) graph

[Henrik_Volkers]

sorry not able to add a picture 😞 nor editing the post :((

[Jay14159265]

So statistically, its this beauty: 

 

It used to solve the 'error in (no error)' problem with error terminals. It had a few other non block diagram default things set up to my liking as well. A close second was a default LV2 (FGV) vi template. Now times have changed so no more vi templates and no more FGVs in my code. Now my most re-used VI is: 

 

[raphschru]

---

@JÞB wrote:

---

@raphschru wrote:

 - A simple and compact error inserter:

---

You want to right-click that Merge Errors and select "Retain all errors" it changes the glyph so, I know you missed that additional option in 2020.

---

Indeed I never used that functionality, but I usually only care about the first occuring error, as subsequent errors may be a consequence of the first error.

I agree it may add useful infos, but then the default error dialog becomes unreadable and a more complex error management is required too.

[crossrulz]

---

@Jay14159265 wrote:

So statistically, its this beauty: 

 

It used to solve the 'error in (no error)' problem with error terminals. It had a few other non block diagram default things set up to my liking as well.

---

I have a similar VI in my user.lib.  I have it in the palettes for both the front panel (change the file type in the file dialog to *.* when editing the control palette and you can place a VI; it will drop the contents) and the block diagram (set to Place VI Contents).

[JÞB]

---

@raphschru wrote:

---

@JÞB wrote:

---

@raphschru wrote:

 - A simple and compact error inserter:

---

You want to right-click that Merge Errors and select "Retain all errors" it changes the glyph so, I know you missed that additional option in 2020.

---

Indeed I never used that functionality, but I usually only care about the first occuring error, as subsequent errors may be a consequence of the first error.

I agree it may add useful infos, but then the default error dialog becomes unreadable and a more complex error management is required too.

---

Then you should:

• Remove the merge errors
• Slap an error case in there
• Slap yourself silly for that

You have written add error if error in is no error

[raphschru]

---

@JÞB wrote:
You have written add error if error in is no error

---

Which is what I want, so why using an error structure when it can be done with a simple Merge Errors.