Leaderboard

For references and more information, see worrydream.com/dbx Presented at Dropbox's DBX conference on July 9, 2013. Bret Victor -- worrydream.com http://vimeo.com/71278954

Use a simple shared counter which every event must go through?

I like the context specific idea. Like some sort of pop up when you click a class wire. Wouldn't be that hard of a modification since I've got all of the logic. It may be a bit of a challenge to keep it on the useful side of things and not slide into the annoying side.

I ran into a crappy behaviour of 5-3-3-5 the other day. I thought I'd be smart (You just know how that's going to end up really) and wanted to connect up two VIs with the same conpane pattern (5-3-3-5) but have them vertically staggered so that the top two connectors of one VI lined up with the bottom two of the next one. Lo and behold, even LabVIEW can't make 32 divided by 5 equal an integer and there was an extremely annoying 1-pixel bend. This may be also the background to some of NI's own 1-pixel benders.

No, definitely not! 4*2*2*4 should be the standard and strictly enforced for all LabVIEW programmers, if I had a say in this! And anyone using the 6*4*4*6 for a VI that is not private to the library should be banned from writing LabVIEW programs.

There are USRs in the ptbypt. That will be a problem. There's a good explanation of how to address this on pages 45-47 of this document: https://decibel.ni.com/content/docs/DOC-30870

Here is the MCL control again (since the previous links in the Thread are broken). Thanks special MCL.vi