Sparkette

Here are the contents of LV_Fail.txt (I am aware the year is set wrong): --- Wed, Jan 24, 1996 2:43:05 PM Failure : "units.c", line 334 LabVIEW version 3.0.1 Please record the preceding information and contact National Instruments for Technical Support 0x001A8F4E MacStackCrawl+204 0x001AA17A Die+38 0x001AA118 DBAssert+128 0x0021C436 InitUnitManager+298 0x001BA1B6 InitApp+1860 0x00198406 WBackground+78 0x00187080 main+32766

For fun. 😄 "Science isn't about why; it's about why not!" - Cave Johnson

Does anyone know how to fix this error that appears when starting up LabVIEW 3.0.1? Failure: "units.c", line 334 LabVIEW version 3.0.1 Please record the preceding information and contact National Instruments for Technical Support I don't plan on contacting NI because I doubt this version is still supported, at least not without a contract.

Even if LabVIEW didn't have this glitch, FOSS programming languages tend to be more popular anyway.

It's worth mentioning that Baba Is You uses Lua as well. (It's not part of the gameplay, but mods can use it, like you said.)

I have LabVIEW 2020 Community Edition installed on Linux, and when I run it, I get the following popup: So I click "Activate LabVIEW Community Edition", and it opens a web browser to a page asking me to log in to my NI account. I do, and then it takes me to a page saying "You have been authenticated. You may close this window." But LabVIEW itself tells a different story: The strange thing is that the "You have been authenticated" page says 127.0.0.1 in the address bar, meaning the message is coming from my own computer rather than NI's website. So you'd think it would match what LabVIEW says, but nope. I'm pretty sure I already tried redownloading LabVIEW Community Edition and it didn't work. Anyone know how to fix this?

Those don't really make sense considering what I did though.

The main reason I'm asking is VIPM for Linux is out of date and requires an old version of the LabVIEW runtime, which it somehow doesn't detect even when I put it in LD_LIBRARY_PATH. I've had issues getting it to work on Windows in the past too, and I'd rather just use a different, less cumbersome tool to install them if possible. Plus it would also be nice in general to have an open-source alternative to such an essential tool.

As a side note, I'm pleased to see that you find my resource editor useful

I'm trying to make a simple, compact, square Boolean constant to put in an array so it looks like a grid of pixels, using XML heap editing black magic. The most significant change I made was converting the multiCosm to a bigMultiCosm so I could color each state separately. It ended up failing to load the block diagram. This isn't a surprise, as I am after all changing data in ways it wasn't necessarily designed to handle, but it did get me curious about what the exact error was, since who knows, maybe it was something I could fix. So I turned on dprintf_logging (in Ned) and tried it again, and this was the output: LoadObjectData error 5, [VI "lvtemporary_436621.vi" (0x000000000a3c9660)], UID 113, tag 'table' (256), dpid 0 LoadObjectData error 8, [VI "lvtemporary_436621.vi" (0x000000000a3c9660)], UID 111, tag 'partsList' (194), dpid 79 LoadObjectData error 8, [VI "lvtemporary_436621.vi" (0x000000000a3c9660)], UID 104, tag 'ddo' (52), dpid 19 LoadObjectData error 6, [VI "lvtemporary_436621.vi" (0x000000000a3c9660)], UID 110, tag 'dco' (48), dpid 21 LoadObjectData error 8, [VI "lvtemporary_436621.vi" (0x000000000a3c9660)], UID 7, tag 'termList' (268), dpid 29 LoadObjectData error 8, [VI "lvtemporary_436621.vi" (0x000000000a3c9660)], UID 3, tag 'nodeList' (164), dpid 27 LoadObjectData error 8, [VI "lvtemporary_436621.vi" (0x000000000a3c9660)], UID 2, tag 'root' (214), dpid 126 I'm guessing the answer is no, but is there any public documentation of those error codes?

1. I thought references to GObjects didn't need to be closed. 2. I'm not concerned about RTE; my interest is for use alongside VI scripting, e.g. for doing low-level editing operations in a shortcut menu plugin. 3. Noted, thanks. I just copied your icon and didn't really consider what it meant.

Thanks; I'll update it when I get the chance. EDIT: Done. I also wired the error in/error out terminals, since I apparently forgot to do that before.

I'm mainly concerned about LabVIEW's built-in uses of the file dialog, File→Open for example. Is there a simple way to replace that with a call to a third-party library?