drjdpowell

I just checked, and it doesn't close teh file reference, but it does pass out a null reference. The original reference is still valid. This is still unexpected behavior, though.

Yes, Queues don't make unnecessary copies, but User Events make two copies, so the EventDVRmessenger is just to work around that.

I have put some effort into improving the VI icons in Messenger Library, in hopes of making things clearer. I have particularly been trying to get rid of the magnifying glass icon, which was standing in for too many concepts. I have also tried to improve the Palettes by putting the standard VIs (that one would most commonly use) in the root-level palette: The 2.0 version also introduces Malleable API methods (the orange-coloured ones), which make code cleaner. If anyone could spare some time, it would help me to have feedback. Especially from people who have not used Messenger Library before, so I can get an idea if the key concepts come across. New 2.1.3 version is available here: https://forums.ni.com/t5/JDP-Science-Tools/New-icons-for-Messenger-Library/m-p/4412550#M192

I'm sorry, you posted just before I went on a full month of holiday and I never saw this. Do you still need help? Any further info?

Has anyone had a chance to use teh new version? At least as far as trying the new examples.

0.6.0 version now on VIPM: https://www.vipm.io/package/jdp_science_postgresql/ This involves significant improvements, as well as Examples that work with a public postgres server (and thus work without needing Postgres installed). I am hoping this is close to a 1.0 version.

I have published a 0.3.1 package on VIPM.io with Antoine's changes (LabVIEW 2017). Then I've accepted your Pull Requests and published a 0.4.0 version as well (LabVIEW 2019): https://www.vipm.io/package/jdp_science_postgresql/

I think your second point is wrong; VIs without the front panel loaded don't use any resources. EXEs don't even include the code for those front panels.

I think this is a Windows touch-screen behaviour, due to Windows using press-and-hold to give a right click. Windows waits for the release before sending "mouse down" so it can decide to make it a right click or not. It's annoying but I have not found a way around this.

Note the WITHOUT ROWID keyword also, as that could make a significant performance improvement with this kind of table.

A non-JSON option you could try is: CREATE TABLE TestData ( Channel, Time, Data, -- individual reading at Time for Channel PRIMARY KEY (Channel,Time) ) WITHOUT ROWID This is every reading sorted by a Primary Key that is Channel+Time. This makes looking up a specific channel in a specific Time Range fast. BTW, you don't need to make an index on a Primary Key; there is already an implicit index . You would select using something like: SELECT (Time/60)*60, Avg(Data) FROM TestData WHERE Channel=? AND TIME BETWEEN ? AND 1717606846 GROUP BY Time/60

Why don't you just try it? Open your SQLite viewer app if choice and execute "SELECT * FROM sqlite_schema"

You're looking for the sqlite-schema table: https://www.sqlite.org/schematab.html

Do you have the latest version of vipm?

Yes, at some point I intend to make an interface that has "to JSON" and "from JSON" methods, that one can inherit from. But at the moment JSONtext is based in LabVIEW 2017.

I will fix the inconsistance, either by making comlex numbers full not supported or fully supported.

Can you give a more specific question?

Not necessarily, but it is trickier than it looks because of those "multipoint paths" that unflatten does not support. A path like $.a.[new,old].b[4].c.d, for example. If all paths were straightforward like $.a.b.c.d then it would be easy. Although I use JSON for configuration, I'm not using it in the same way you are doing, so it hasn't motivated me to solve this issue. Sorry.

See if "Unflatten JSONpath Array to Object" will do what you want. It will create the extra levels if needed.

That vipm package seems to have gotten corrupted somehow. I'll contact NI about it. In the meantime, try getting it from here: https://forums.ni.com/t5/JDP-Science-Tools/Out-of-Memory-Error/m-p/4335019/highlight/true#M156

Can you try forking the repo? Then making a pull request? I only have a free Bitbucket account and there is a limit on how many people I can add to my repos.

Compiled object cache is an SQLite database, I believe, so is suspect you can easily delete VIs from it. Though you'd have to test that.

I'm afraid I don't have an example. I did once prototype a version where I swapped out the flattened message format for one that used JSON (I recommend JSON as an easy, reliable format to go between languages).

I use the "Advanced PNG Export" feature of https://pictogrammers.com/library/mdi/. This allows some customisation of icon (size, colour, transparency, border) before downloading.

Why are you making Setting modules at all, rather than just having the other modules just read the INI file directly? This seems very over complicated.