hooovahh

Reading the whole file and modifying it in memory is probably the only decent solution. That being said there are a few DLLs that can be used to modify ID3 information. Here's a few sites of which I haven't personally tried. http://id3v2.sourceforge.net/ http://id3lib.sourceforge.net/ http://tomorrow.uspeoples.org/2013/02/powershell-id3-tag-editing-via-taglib.html

I've been using the Simple Sexy timing probes for years now and they are very similar. https://decibel.ni.com/content/blogs/EvanP/2010/10/04/simple-sexy-labview-timing-probes They also have the ability to pause an execution if time is greater than some value.

What are the tablets running? In a Windows environment you could synchronize all their clocks (to the ms) then when your program runs, send over TCP the time stamp of the event. Then when your host system gets a buzzer, let it wait say 100ms for any other contestants to buzz in with an earlier time stamp.

Neat, thanks. I think there are a few operations that could be simplified but lots of neat nuggets in there.

Heres a good start. I don't really have the time to do all of it. Provide a path to the Main VI, then run this. I will find all callers of that function, then in each VI look at each subVI. If the subVI called is the error one, then it opens a reference to the terminal, gets the source of the wire, opens a reference to a constant wired to it, then gets its value. I think I forgot to close all opened references, and this has an output letting you know if something other than a constant (or nothing) was wired to the error code (0) input. Find All Error Code (0) Constants.vi

Software is not data, gotcha. BWAHAHA

What would you consider ad hoc reuse? Someone comes up my desk asking "Hey how would I perform a partial search for a 1D array?" If I show that user code that does this, and the user redevelops that code based on what I told them, is that reuse? What if I send them that VI in an email? Is that reuse? What if I point them to a forum link online showing someone who posted code on how to do it? Let all agree a formal process of release is better, and does take more time and effort. But isn't some of these thing in between considered reuse at some level? It isn't easy to track, and so usually when I say something like "This project is 50% reuse" I'll usually say this project is at least 50% giving the reasoning why some reuse can't be tracked.

So...instead of asking a question you made an article, which is usually used for showing people how to do a thing. And instead of showing someone how to do that thing you asked the question? Then in the forums where you would ask the question you just link to that article? Why didn't you just ask the question here? I've edited your post so the question is in the forums where it belongs. As for your question what have you tried? Have you searched this topic, I remember finding several semi-working solutions involving hidden path controls.

Not sure if you're aware of this, but 2015 is supposed to cache bookmarks in a much smarter way to improve these issues. I can't say for sure, since I didn't use it much before 2015 so I'm not aware of many slowness issues.

Looks pretty good to me. The only improvements I could suggest (which I tried and have no real effect) is to disable debugging and automatic error handling, replace compound arithmetic with the native AND and OR. And I would assume LabVIEW could look up stream and find that the boolean array output isn't used and might optimize that away. But adding an indicator (outside the for loop with the other indicators) didn't change the result of the test. So in this situation LabVIEW does its job better than we can. Or rather the compiler can use things it knows and create code that performs better than we could create. And honestly this is one of the staples of LabVIEW programming. "Don't worry about it the compiler will take care of it." This statement is both something I've relied on, and something I've hated at times. The compiler isn't perfect, but I obviously trust it enough to rely on it daily.

Yeah some of us are dumb enough to actually host our first crapware. To be fair I think that is probably my second crapware attempt since my first attempt is gone forever. Once I discovered LAVA I realized that would be a better home for cleaned up code so I haven't put anything new on there other than the tray launcher which has EXEs and installers that I don't think LAVA would like.

Eh, it depends on how it is measured for sure. Back then there wasn't the code complexities that was added in 2012 or so, so coming with reuse metrics could be up for interpretation. I've used the code complexity for a reuse measurement metric in the past, and then broke it down into things like OpenG reuse, MGI reuse, vi.lib reuse (is that cheating?), and other reuse. Then there is reuse that can't really be measured like copying an existing library, or whole project from some old code (data mining), where here reuse is between 0% and 100% but code can't really detect the exact amount. Edit: I should probably force myself to get some free time and release my reuse metric, unless VISTA is going open source

Yeah I made a thread, and then eventually a utility that attempts to make standard bookmarks easier to add. It can be invoked from the tools menu, or with a little work from a quick drop. It brings up a window that shows all the standard bookmarks, along with descriptions of each one. There is some that could ask for more information too, like a tag that is covering a requirement, which then asks what requirement to put in the comment. There is also a scan option for finding all tags already in a project. I honestly don't use this all that often, but I made it hoping it would encourage me to use the bookmark manager more.

What's your relationship with this customer? Will they beat you up on price and get you to agree to (X+Y*Z+W)*0.6? I don't have much experience with quoting freelance stuff. But in larger competitive bidding generally sales will tack on some percentage for overhead, then another percentage for a buffer expecting the price to be negotiated. Of course when you tell sales the bottom price will cost $100K, then they tell you the bid was won for $50K, engineers tend to get a little upset. (I'm not bitter, honestly)

LabVIEW can do some funny things, with constant folding, deleting dead code, and caching results from previous calculations. That coupled with the fact that UI elements are updated asynchronously, probes, automatic error handling, and debugging, can cause code that measure execution speed to be some thing that is trickier than initially thought. You may want to post the code you made which calculates this speed test so we can determine if it is calculating a speed properly.

We've used a couple but the one I remember liking was by Supermicro, can't seem to find the model. A new standard 3U or 4U rack mount computer is probably going to be around $1K, but I think we budget for $2K. Something that looks like this one, but no with 8 ISA slots. http://www.superlogics.com/industrial-computers/rack-mount-pc-computer/SL-4U-SBC-H61-HA/269-5133.htm

Disclaimer that a lot of my knowledge on this subject is not from hands on, but research. I have lots of experience with cDAQ, and lots from FPGAs, but not so much when it comes to RT or embedded targets other than FPGA. When using a embedded target, you'll program on your normal host (usually Windows) machine and in the project you will add your target. Then you will write VIs for those targets and deploy from within your host. Then some level of debugging is done on that host machine, for the code that is running on the target, this always involves seeing front panels, but also some level of probing for some targets. (for example FPGAs don't allow probes breakpoints etc.) When using a cRIO almost all I/O go through the FPGA. There are exceptions for things like serial ports which I think just show up as a VISA resource. So full cRIO applications may have three targets, the FPGA, the RT, and Windows, all in the same project. But for debug you can temporarily ignore the Windows target, and for the FPGA you might be able to get away with the Scan Engine, which is a FPGA profile that just reads all data and sends it to the RT. So you might be able to get away with just needing to write one program, but then when you need more control you can write code for the FPGA, and then a custom UI might be needed on Windows. All three targets have the familiar LabVIEW IDE, just some have a subset of palette items. I have never used an embedded cDAQ chassis but I believe they are a target in the project and you write code and deploy it like before. But in this case I/O go through DAQmx and not through an FPGA. A lot easier, but less flexible.

I also think this is 2014, without any confirmation.

You know what I think is rube golberg-ish? Having cameras, vision, head tracking software, and lights to press a key. I think the foot pedal works, not that I don't think nodding for stuff doesn't sound fun.

Yes, a value change event does not necessarily mean a different value than the previous one. You can use the Value (Sig) property to set a control to the current value and the event is still triggered, same with this. The solution seems like an easy one. If the old value, is equal to the new value, do nothing. The old and new values are available in the event that is triggered.

Filthy Casual. But seriously yes I type with my hands on the home keys (stupid Mavis Beacon made sure of that). Swapping too many keys can be dangerous when I go to use literally any other keyboard in the world. The other issue is changing my brain to use keys differently. CTRL has always been that very lower left key, I can feel around to find the edge and know which it is. Changing CTRL and ALT sounds dangerous. As I mentioned I already replaced Caps Lock with CTRL because I just don't use that key.

Okay a quick update. I tried some behavior changes to make my life easier. I did get one of those Kinesis keyboards I linked to earlier (used cause who whats to pay that much), and I got the adapter that lifts the center of the keyboard and has the wrist guard. This is a bit difficult to get used to but I like it. I also bought an industrial foot pedal like this one, wired it to a Teensy LC (cause I had one already) and using the internal pull up I have it activate the CTRL key when pressed so I don't need to stretch my pinky finger. This change is harder to get used to because I need to have my foot in a resting position but ready to press, and then force myself to use that instead of my hand. It's possible and I use it for about 50% of my CTRL presses. I also went to the doctor and they said I have tendinitis which is a catch all term, and the specific injury might have a better classification. I'm now going to physical therapy for a month or so for some hand and wrist treatments. I'm also doing some hand stretches, and am doing better. As for the desk, I'm sorta in a lab environment without much extra space. The desk is a solid one that doesn't adjust, and probably a bit too high. I don't think changing it would be easy.

Oh that reminds me, XControls have some kind of limitation when it comes to using user events, I believe you can't use user events at all, that are created from outside the XControl, and I wonder if when it executes and registers has something to do with this limitation.

Thank you very much for the correction, I've edited my previous post. For answering several questions in this thread I went and wrote code to confirm my assumptions. When it came to answering that question I just assumed I knew what it would do but as you mentioned gave the right answer to a different question.

I never really messed with this feature much, so I had to write some test code to see. It appears the locking of the FP occurs on static events when the event occurs, not when it is dequeued. Same goes for dynamic control references, if the register has the "Lock Panel Until Handler Completes" by right clicking the register for events. As for user events, it appears this isn't an option because user events don't involve UI controls.