Meeting 14-03-2024

[Freel]

Dear DutLUG community,

I hereby announce the presentations for our next DutLUG meeting in March.

Please note that alle presentations will be in person, we will not be recording or live streaming and all presentations will be in English.

Stay healthy and see you all soon! 😊

*Important message*

Exciting news for our LabVIEW User Group! Our upcoming event is not just limited to Eindhoven, Netherlands, but also extends to Zellik, Belgium. We're experimenting with a live connection between these two Benelux locations. Join us in one of these two locations for this experimental collaboration. Just like in Eindhoven, Zellik will provide tasty food and refreshments before the presentations start. It will be possible for people attending in Zellik to ask questions. Register for our newsletter for more details. See you there!

---

1. Albert Geven - Coding Configuration Files: A Case for INI and JSON

In this presentation, we delve into the considerations for choosing configuration file formats, focusing on INI and JSON files, inspired by Stefan Lemmens' talk on December 14th last year. We explore why one might choose an INI file for its simplicity and ease of use, particularly for straightforward applications, and contrast this with the flexibility and nested data structures offered by JSON files, suitable for more complex applications. The discussion highlights which choices must be made, considering factors like readability and ease of implementation. By drawing on real-world examples and best practices, we aim to provide guidance on selecting the appropriate configuration file format for different software development scenarios.

---

2. Bram de Bruin - Managing Custom Errors

Have you ever experienced that moment when you can't see the forest for the trees because, after six months of development, there are so many custom error codes in the software? And then there are errors that pop up which aren't on the meticulously maintained list? Since LabVIEW does not provide a smart management system for custom errors, we've come up with our own solution. In this presentation, we'll explore the different options for custom errors and our approach to managing them, along with some detours into tweaking your project environment for better efficiency.

[rolfk]

Wanneer is het mogelijk om zich in te schrijven voor dit? Op de EventBrite site is maar een entry voor een gecanceled event op 9 February jl.

[Freel]

---

@rolfk wrote:

Wanneer is het mogelijk om zich in te schrijven voor dit? Op de EventBrite site is maar een entry voor een gecanceled event op 9 February jl.

---

Het systeem is aangepast, vanaf vandaag kunnen jullie je inschrijven. 🙂

[Albert.Geven]

Hello everyone

Thanks for pointing me out on JSONtext, I finally made the app work and will now rework it into a JKI state machine to minimize the stuff needed.

The real problem was a problem in the writing of the JSON string, forgetting {} around the whole object.

So not only the wrong connection to the value node.

And April 2 a small update, removed the test for .JSON and updated write for JSON to prevent latched Booleans to generate an error message.

April 9 added a @version.ini.json string with content "0.0.0.0". And sorted the controls before writing them to disk. so that @version appears as the first json var in the text file.

It is not a good idea to have this version control at the front page at least not as an editable control, but this is the simplest way to show a possibility. Only update the version control string if absolutely necessary and check when reading. ( by the way putting a transparent drawing over the version control string makes it more difficult for a user to change the version...)

[Albert.Geven]

I finally succeeded in finishing a good working program after fighting with the select  file for loading and save as. I still have a test if the .json is available in the chosen file name but I guess it is superfluous now I selected the correct file properties in the express dialog.

Added to this reply is the coding in LV 2017 to have as many people as possible use this example.

Some more explanation is given in the .ppt file that is an adapted version of my presentation during DUTLUG. 

If you have questions, post them here or on LinkedIn or send me an email on albert.geven@gmail.com

see earlier post for the files