ShaunR

So does that mean that comms primitives (TCPIP, Serial, Bluetooth etc) are all going to be changed to arrays of U8? Strings/data....it's symantics. If it's not broke...don't fix it.

I never said it was. I was simply pointing out that NI wouldn't "cry" over a password protection hack and that since the licensing has been compromised; they would be more concerned about that-if at all

I know nothing about Ruby...and probably never will. But I would imagine the test tools for it are aimed at that environment in the same way as they are in Labview and (probably) not compatible. If you want to manage your tests in Ruby. Write the tests in Ruby! Whats the point of mixing and matching technologies and the headaches associated with getting them to play nicely (activeX springs to mind). Agile development is language agnostic. It is also discipline independent since it is a group of project management methodologies. So the answer to how do you implement it in Labview is "the same way you would for anything else". I personally use M$ Project and. at a push, will use Excel - it's not really important. The key point is for some of your incremental release gates (cycle results) to coincide with major milestones on a more encompassing, linear plan (since that is what the upper echelons of management prefer).

Nope, It affects the users more than NI. Ni are probably more worried that their whole licensing scheme has been compromised since 2009.

If it is..... I would choose No3. Each module is configurable to do No1 or No2 to it's immediate owner.

The year that it all went wrong

You are changing the requirements now

Or-ing "THE" =0.

Just OR the =0 with the stop and it will work without an extra occurrence and without a timeout..It is a sequencing issue rather than a race condition-as with AQs version.

I stand correct4ed (when did they add that then?) IMHO this is how the other primitives should behave (and that includes diagram, project and control refs). I've lost count of the number of times I have had to correct others' code because the refs aren't closed. It is these primitives that are counter and intuitive rather than the occurrence. Oh for the days when Labview meant you didn't have to worry about memory leaks. Seems to me that they work similarly to a notifier (since they have a timeout) without the pit-fall of memory leaks.

Because the local variable will be evaluated well before the first loop reaches the large number and will present a FALSE to the stop terminal. Everything (in the second loop) then waits for the occurance. Once Loop 1 actually fires; loop 2 then proceeds with the FALSE, goes around again and then waits, once more, on the occurance-which never arrives since the first loop has already terminated. This is why no-one uses them. Its too easy to get race conditions that hang your app because they don't have a time-out. It will work correctly IF you put the occurance and the local into a sequence structure that guarantees the local is read AFTER the occurance (another reason no-one uses them since they don't have error terminals and forces you to use those pesky sequence structures.)

That won't work.

I just set the block diagram background colour in the preferences. I use a different colour for each LV version so I'm aware of what version I'm in. I also use it as a "completion" indicator". I start out with all the diagram in a colour and set cases, frames etc it back to white once that frame/module or whatever is completed. That way I (or my colleagues) can see at a glance where I need to do some more work. Yes. It sticks with the vi.

Should you really be asking that question?

The byte sequence will change every re-compile-so it is unlikely to persist exactly as in that post across versions or even the same versions with different bitness. But at some point you have to say "Is it? or Isn't it? a correct password" and finding it is easier if there is a dialogue since you know where to start. I think most of NIs password protected files are purely to hide the terrible coding. Not that bothered if someone sees mine.

Ahh. I see what you mean (I thought it was at least in Dispatcher-have to check) Here they are).

There is nothing special about the clear error. It is just a control and indicator unwired. These are my versions of the clear error and clear specific error (you can find them in many of my submissions to the CR) that uses far less realestate and can be placed between property nodes (and similar) without having to route wires around.

Just one final thought on this (probably not relevant). I have seen exactly what you describe when a machine has Bluetooth . The 5- 8 second freezes go away when the Bluetooth adapter is disabled. I never got to the bottom of this since the machine didn't need Bluetooth, so I just disabled it.

Good point...... Don't forget to press the "Generate" button to regenerate the product code in the version page if your copying an installer.

Not really.....but... The project file is xml. So in the past I have cut and pasted the section <Item Name="Build Specifications" Type="Build"> ..... </item> and it worked fine.

Yup. I do it the same way as sachsm.

I thought I already was . Isn't my name on an openG FP somewhere?

Naaah. I'd prefer it like like JGs. You would have made a huge profit in only 3 weeks.

I believe it is (or at least a wrapper for it). This is the prototype it (TCP Get Raw Net Object.vi) uses as the call to LabVIEW int32_t NCGetRawNetObject(uint32_t nc, uintptr_t *netobject); It is just a typecast to get the nc parm from the connection ID.