Leaderboard

Hi, just a work I've done few years back, toolkit for power systems simulation. All elements are Xnodes. Cosmin

New non-xnode update for "Re-Label Wire Xnode" popup plugin Relabelizer.llb , copy to ..\LabVIEW <version>\resource\plugins\PopupMenus\edit time panel and diagram.

This thread got me to reorganize my workspace and project structure to most importantly improve load and build times and reuse workflow. It came to me as a surprise that LVLIB's although great in some ways force static links to everything in the library. I had previously seen this with classes but for some reason didn't expect the same from LVLIB's. Anyway, I ended up breaking apart a lot of reuse code and restructuring a large project. This seemed obviously a pretty daunting task at first and I was looking to utilize the "links" application by JackDunaway/Wirelabs. Unfortunately, I didn't manage to get it working fully so what I ended up doing was grabbing the hidden "App.Read Linker Info From File" invoke node from the code and searching the list for items where links jump to unintended libraries etc. The few hours of work were definitely worth it and I can recommend similar procedure to anyone starting to see the effects of unwanted coupling.

I just started developing a LabVIEW 2013 driver for MongoDB . Currenly working with JSON only. https://github.com/3esmit/LabVIEW-MongoDB Name: LabVIEW MongoDB Category: Database LabVIEW Version: 2013 License Type: BSD MongoDB Is a NoSQL database. It store documents in collections instead rows in tables. Tow collection documents don't need to have the same structure, and a document can store another document or an array of documents. Each document is persisted with "_id" containing a special type called ObjectID. This lvclass deals with .NET dlls drivers from version 1.8.3.9. Later versions maybe cannot be used (I could'nt make them work in anyway) since LabVIEW 2013 ignores important functions from later drivers maybe for not supporting some .NET feature it uses. The 1.8.3.9 driver got a bug in list collections that is worked around in the lvclass method. Features: Deamon Start/Shutdown Insert Document Find by ObjectID Aggegate List databases & collections Create Collection Remove by ObjectID Find by Regex Find By Equal Get Document Part Update Set Insert Variant Planned features Find Variant Aggregate to Variant LVOOP ObjectID LVOOP BSON LVOOP Query LVOOP Aggregate

This can be done by using subpanels to subpanel VIs containing one splitter bar and two subpanels to create arbitrary splitter bars (recursively). However, this technique tends to crash LabVIEW. WARNING: These examples will crash LabVIEW. [Moderator Note] This post contained some kind of attachment links which could not be found, so they've been removed. A best effort was made to find these missing attachments but unfortunately could not be found.