hooovahh

Yeah I didn't know how far back to go. I didn't use 5.x, and 6.x much but from what I remember it followed my semi-pattern. 5.0 - Stable 6.0 - Not Stable 6.1 - Stable Don't ask me to go back farther. You know my projects have alot of CAN/XNet stuff it could be the driver I guess.

I have a problem where basically all versions of LabVIEW will crash on exit occasionally. 2013 is no different. I suspect it is a system setup rather then a stability/instability of LabVIEW. Traditionally NI (intentional or not) skips a version when it comes to stability in my opinion. There are exceptions to the rule. This list is just my experience and you're welcome to disagree. 7.0 - Not Stable 7.1 - Stable 8.0 - Not Stable 8.2 - Stable 8.5 - Not Stable 8.6 - Not Stable 2009 - Stable 2010 - Not Stable 2011 - Stable 2012 - Stable 2013 - TBD Is there a rule about software releases where every other version is good? I feel like Windows follows this same rule.

It is? Well then there should be no reason to not put it on the palette right

Maybe that's it, maybe they used the High Resolution Relative Seconds to get a more accurate time? Most likely this is not the fix because I think the high resolution time is Windows only which is why it isn't on the palette yet (just speculation).

I've seen something similar with TDMS and Copy. I have a test running where we log to TDMS. Then we close the file at the end, then copy it and the index file to a duplicate location. Many times I would get an error 10 "Duplicate Path" "Asynchronous I/O Operation In Progress". So I would put the copy function in a for to retry a couple times and we no longer have this problem. I never determined the cause, and didn't have time to debug it because a solution was found.

I just tested the VI attached by AQ in the first post in LabVIEW 2013. I clicked Trigger about 20 times, and every time the user event was handled first, and the array showed 0, 1, 2. It does look like this is fixed. I do wonder however, what other event based bugs will be seen now that 2013 had this major overhaul. I don't believe there must be new bugs, but it looks like there was quite a few changes, and I'm sure a lot of testing went into it, but when upgrading legacy programs I wonder what unexpected results may occur.

So a couple things. If you have a professional version of VIPM on your laptop you can create a VIPC file that contains multiple packages. This will create a single file that can be double clicked on any computer without the internet and it will install all the packages just as if you got them from the internet. If you don't have the professional version of VIPM you can still copy the individual package files from your laptop and bring them over. Go to C:ProgramDataJKIVIPMcache to find all the packages that have been locally downloaded. This path is for Windows 7 and maybe slightly different for other OSs. You can then install these package files on your other PC by going to File >> Open Package File(s) and selecting all the files at once.

I can't help but get excited. Because everything this guy talks about resonates with what NI has been trying to do with LabVIEW. Also the fact that people rejected Fortran made me smile a little. Because the same type of people, will reject LabVIEW for similar reasons. Not that I can't be suborn at times. I still don't use the auto-tool.

I started calling myself LabVIEW Overlord as a joke, because people throw around the term Guru all the time. Only now it sound pretensions when someone introduces me as the LabVIEW Overlord. Also someone may take that as me pretending I'm better then a NI Knight, which wasn't the intent either. Lets not be rational here. We can all agree it is NI's fault and I demand they fix it. Can't they just have 6.4 pixels per terminal?

I agree. I have found myself developing a tools menu item, and then changing it to a quick drop item instead. When developing I find two shortcut combos is faster then navigating the tools menu. Especially on a system where the items and order of the things in the tools menu potentially changes after installing something from VIPM.

I'm no quick drop expert but this is how I'd do it. Say CTRL+Space then CTRL+C (maybe that is semi-reserved) this brings up a new dialog window that shows the options, and you pick the one you want which then adds the code to the block diagram. Closing this window does nothing, and calling another CTRL+C brings this window back to the front with new settings if it was never closed before. Not ideal no but I think it could be used this way.

I forgot about this. But usually to highlight this I will color the background a different color, or bold the font. I don't think either of these change the cell height.

I'm okay with this for the same reason. But I would rather be consistent. Look at the sample I posted with the TDMS functions. That gets me every time that I need to be one pixel off whenever that palette is used. I would rather they were consistent with 5-3-3-5 (or what ever they picked). But I would say that 4-2-2-4 is my standard and very rarely deviate from it. But just as the style guide is a guide, I would say that a 4-2-2-4 setup should not be strictly enforced and if I were king of LabVIEW I wouldn't ban anyone if they used another.

Yes there exists properties to modify the graph axis info. One demo (that I haven't found yet) was shown off at NI Week to allow a graph to be zoomed in using the scroll wheel. This was to show off the new mouse scroll event. Select the active scale property for either the X or the Y scale. This is a zero index value so if your graph only has one X and wire a 0 to it. Then you'll probably want to change the autoscale to be no auto scale. Under the X Scale Property set the Scale Fit to 0 which is no scale (the help describes the others). Then you can set the X Scale, Range, Minimum and Maximum. This will set the minimum and maximum that the X will be. You can do the same for the Y scale as well.

I wasn't at the challenge but I could tell there was some kind of discussion there about the implementation. It met the specified requirements did it now? I realize it may not be the intent but that is because of poor requirements. Now that I think about it I can agree with your front panel specifics, because you mentioned what is considered an object on the front panel from the perspective of LabVIEW.

Yeah when Christina mentioned the cell height of each cell needs to be the same, I thought when have I ever wanted the cell height to be different for a single row, and I guess there is a case for this but I have never needed it.

I'm going to argue for the sake of arguing if you don't mind. "To stop the VI you cannot press the abort button, or by clicking an object on the front panel" Are we now saying that the exit button is not an object, on the front panel? The title of the window is something like "Untitled 9 Front Panel" so to me that states that the entire window is called the Front Panel, and the Resize, Minimize, Maximum, and Exit buttons would be part of it. That being said it doesn't bother me that Darren won.

Maybe I made a superBoolean class that is a subset of the boolean class that I want to be more specific to. Or maybe I just grabbed the first two functions I knew would demonstrate my frustration and took a screenshot.

I don't use auto tool (lets not get this started) so I am very quickly pressing tab, on top of all the quick drop functions, compulsive CTRL+S, and constant CTRL+E or CTRL+W. As a result I have been called the Certified LabVIEW Finger F***er.

Instead of 12 Steps we have 12 States. We admitted we were powerless over LabVIEW OCD alignment—that our lives had become unmanageable Came to believe that through hard work and determination, ourselves could restore us to sanity. Made a decision to turn our will and our lives over to the block diagram cleanup as we understand it. Made a searching and fearless moral inventory of ourselves. Admitted to ourselves, LAVA, and to another human being the exact nature of our OCD. Were entirely ready be content with these wiring defects. Humbly asked developers to review their code and accept it when the review is complete. Made a list of all developers who did not adhere to the LabVIEW style guide, and became willing to make amends to them all. Made direct amends to such people wherever possible, except when to do so would injure them or others. Continued to take personal inventory, and when spending too much time adjusting wires, promptly admitted it. Sought through research and discussions to improve ourselves, for knowledge of other developers for us and the power to carry that out. Having had a acceptance and realization as the result of these steps, we tried to carry this message to other LabVIEW OCD wire addicts, and to practice these principles in all our affairs. You would be surprised how little this differs from the actual 12 steps.

I am all for this type of development, and I think I can see how this could help with that. Thanks.

I don't fully understand what you are saying but am curious. I have used event call backs on .net DLL calls so I am passingly familiar with them but I don't know how they could help simplify my code. So when the mouse enters my panel VI I can have that run a VI through the callback feature, which can generate a user event, that tells the parent this event has happened? I don't see how that is better then at the moment where the VI ref can be passed to the parent, then register for the mouse enter event, causing the event to be handled in the parent when the mouse enters the panel. Don't take this post as me saying "This is stupid and my way is better" I just don't fully understand how it can help because I've had very little experience with event callbacks.

Okay I don't think I'm as bad as some of you guys but I too find my self moving things one pixel at a time some times to line them up nicer. But there are a few times that I hate the terminal choices used by NI. Here are two times that I can think of that irk me. Why do these not line up? Seriously NI? Seriously?

Very true, you could flush it then process the last one that was flushed. I haven't used the new Event Features yet but I assume after flushing it will return all the events that were flushed like a flush queue. Then if 100 value changes come in you flush them all and process the analog output on the last one. There's a bunch of ways of working around this and the timer idea neil mentioned is another I have used.

Okay it's morning and I have a few more links. Inlining INI key http://zone.ni.com/devzone/cda/pub/p/id/347#toc2 Thread discussing it and code http://forums.ni.com/t5/LabVIEW/Dr-Damien-s-Development-Improve-Load-Time-with-Inlining/m-p/823418