drjdpowell

JKSH has explained as well as I could the expected use. "Missing from Object" is determined when operating on the Object. I had a look, and it should be reasonably easy to give a different error for a string with only whitespace, but I'll need to understand use case for it better. I, personally, never find the need to write custom error-handling code. By the way, if one's use case is "set from this JSON as much as possible, or use supplied default for items where this is not possible", then one can just not use the error wires at all.

I am actual about to commit to making the next release in LaVIEW 2019, rather than 2017, as VIMs were very new in 2017 and both buggy and of limited capability.

Use case? Why do you need different custom error than the 402841: "Invalid JSON formatting" that you have now?

Since Latin for six is "sex", we could have gone for "sexidecimal".

So? Main.vi knows it might need disposing, as it did the creating, so do the cast.

Note that System could have a method to remove the Transport ("uninject"?). Main.vi can remove the TCP and dispose of it, just before it disposes of System.

The problem I have with the Network Streams QoS arguement is that TCP already does this, using ACKs and retries to ensure an ordered stream. And if I really needed to be sure a message is handled, I need to verify it all the way through the application to the final result, not just through the Network Stream message delivery. For example, if I need to send something to be saved to disk, I need QoS all the way to disk, and would have to implement a custom buffer on the send side, layered on top of Network Streams.

I've never used Network Streams. It appears to me to be an API that makes TCP communication easier, for a specific use case of a one-way stream. But I've seen, on more than one occasion, people use it build APIs for entirely different use cases, ones that would (in the end) be simpler and more performant to base on straight TCP.

I've done this kind of thing, with a 32-bit-only dll needed from a 64-bit one. Actually, it was two 64-bit Test Stations that both needed the same info from the 32-bit equipment, so having both be Clients of the 32-bit Server worked well. I used the TCP capability of Messenger Library, which is very little effort. One question: why Network Streams? If you are wrapping things in your own API then why not a standard TCP connection? What are Network Streams giving you?

Your DB Browser and LabVIEW are possibly using different versions of sqlite. Can you run this in each to detect the version: select sqlite_version();

Does anyone actually use Variants in clusters in this way? To me, this is not even a tertiary use case of JSONtext, so it would be helpful to hear from people with real-world uses. I am tempted to suggest throwing a "Variants not supported" error, but even that would add overhead which I am loath to do.

Can you attach a small VI demonstrating the error?

Please try this fix: jdp_science_jsontext-1.6.6.106.vip

Issue 92: https://bitbucket.org/drjdpowell/jsontext/issues/92/all-integer-types-needed-for-set-map

Again, Variants are tricky, and have two names and serve two purposes. Viewed as a container of named data, your Variants are just placeholders, not actual data themselves (which is why I suggested in the last post to put a named Variant as Data inside the placeholder).