todd

... changing the file to be read-only maybe an easier alternative for this...

If you have the "treat read-only VIs as locked". Otherwise, dirty dots can happen.

Distributing code that is "locked - no password" works no matter what LV settings someone else has.

1) "Create User Event"

2) Make that event (the wire) available to all the VIs that will generate it or respond to it.

3) For each VI that should respond to it, "Register for Events". Only wire that event ref to one event structure (ES). Other ES can register for the event, too.

Cool! Thanks for sharing!
By the way, a variant constant's class name is "constant", which is missed by the scanner.

http://labviewwiki.org/Bug

points to:

http://ni.com/ask

which goes to where Ton pointed.

Just mentioning it to see if it affects a LAVA forum search for "Bug Report".

Will the "Strings[]" property node work?

Oh, right! In "UI.Enter Pressed.vi". Nice.

A boiler exam attempt is here:

http://forums.ni.com/t5/Certification/Sample-Exam-Solutions-for-Review/m-p/2385580#M738

I've been working on "real-world" code to see if some of the pros, here, might review it - but as soon as I get each piece close to ready-for-public-eyes, I become comfortable enough with it to switch to customer-specific instances.

Premature report...

Ok. Still Pro, but the idea is here: http://ideas.jki.net/topic/167870-allow-locked-no-password-protection/.

Looking again, under Source File Settings, there's an option to add a password. That's not available in Free. Does Pro allow you to select Password Type "Custom", then leave a blank password?

Yes, the Send Normal Stop. I've been working through the details of proper error and last-ack handling, so it jumped out at me.

I've had a few simple actors not let me close the Actor Core.vi override front panel, even after they've stopped. Nothing repeatable, like you have, though.

It doesn't help anything, but in the top-level Stop Core.vi override, shouldn't Send Stop be outside the error wire? Instead, perhaps, send normal or emergency stop with the code from Error In?

I have not. There's some kind of protection tab in the Pro version, though. Maybe it's in there.

Cut the top edge, and it falls in a pile on the ground - then fling it around the screen. This is lovely.

Two ES in one loop is generally bad form, yes - but they each have a 100ms timeout. That won't hang.

Ha! Only tried it once, for a kind of record-and-playback scrubber with multiple cursors, annotations, scroll bars, buttons, etc. I started with the XGrapher example on NI.com, which was nice. I soon made things more complicated than they needed to be. I mean, I soon realized that wasn't the best fit for an XControl.

My group had only minor inconveniences (dinner reservations cancelled, aquarium was closed, a few T stations closed). What surprised me was how calm everyone was. They didn't announce anything, but the police and EMTs were racing past - and I only heard of one small area where people panicked and ran.

For error info, can you just override "Handle Error.vi"?

My forever-girlfriend finished about 15 minutes before the first bomb. We were waiting for her about a block from the finish. Here's a before-picture. Oh - no pics on mobile.

I've been using Mercurial and bitbucket.org, for the last couple of months. Command line hg and TortoiseHg both work fine. I do not use the built-in LV SCC. No Git experience. Have you seen the Git User Group on NI.com? https://decibel.ni.com/content/groups/git-user-group?view=blog

The boiler ended up being much more suited to AF, in my opinion. It took me about six hours, but I added functionality that's not in the spec. Also, I wanted to use it to ask some practical questions about the theoretical statements of AOD.

LV2012, AF package 4.1.1.33

my AF Boiler Solution.zip

That happened to me, the other day - added a value in the middle, and some constants changed. I have the vague recollection that a case structure changed, too. No time to repro and capture.

I may try the CLD test in a couple of weeks. Here's the ATM exam written in LV12 with AF package version 4.1.1.33.

This took me about 4.5 hours (though I had to pause overnight at 2.5 hours). I didn't do any planning at all: code-and-go all the way.

The UI is the only actor. I really wanted to make the file I/O an actor of its own, as well as a countdown timer (so their FPs could be shown during DEBUG==True), but I'm not THAT fast. Overall, I'm happy with it, for the time spent. Comments are welcome.

my ATM AF Solution.zip

Not sure it helps you, but I noticed:

When I closed those two projects, the LV icon was still in the taskbar.

I opened another project and happened to view the class hierarchy.

The Server and Client projects are still there, and PN App Project.Projects still lists Client and Servers projects.

Heh - crossed posts, again. I admit to occasionally being beer-motivated.

I got one of the project ref leaks to go away by fiddling with: Get Remote Application Reference.vi

You can type-cast a ref to I32, then format into hex string and feed it to "Generate User-Defined Trace Event" on the BD.

"Get Remote Application Reference.vi" gets refs to both projects but only closes one.

That VI matches the guess I made.

Yes, I tried server-first and client-first.

Turns out it was the server port. I have 2012 on 3365. Yours must be 3364.

DETT reports a project reference leak reported in Get Remote Application Reference.vi, and an Application Reference Leak.

Ah, you ran it. I have LV2011 on 3364 and 2010 on 3363.