Leaderboard

It's just tu pun together some pics from this topic and little bit more... So we already saw that wires may go diagonally: Then that they may have almost any shape: Michael showed us how execution dots propagates on such wires: Link Sources for creating such wires here. Now I'm getting crazy. Sit down, fasten your seat belts, hold your breatch and watch this. Although it does not run too fast (no more than 10 fps on my computer) but Jing slowed it down even more, so in real everything happens much more smoothly. If you would like to play with this: controls or nodes which have labels are fixed to backgroung. Don't change damping too much. Don't put too much objects on BD. Always wire both inner and outer terminals in tunels. Sources attached. spring-wires.zip

I recommend everyone getting into it - as now I don't think I would want to code an app without it. It was (and still is) a lot of fun to learn and program with. The only issue I have is that my dev environment crashes alot (and I mean alot) when using it and I hoping this may have been fixed in 2009 (or occur less frequently). In order to learn it I thought the best way was just to dive in head first do all the examples, read all the white papers, watch all the on demand videos and just start using it! Around last year, I thought to myself that LVOOP was the way that NI had chosen to go with its OOP implementation so I decided I wanted to get into it and use it seriously for client apps. At the time I was confident that LV8.5.1 was a very stable release for LVOOP - I had heard of some issues with its initial release around LV8.2. We then moved up to LV8.6.1 internally and LVOOP had more features and improvements - which made it even better. Its great to see once again that LVOOP has evolved a lot in 2009, and that it is starting to get used all over the place within LabVIEW. So I am very confident that NI will continue to support it and will keep improving its implementation. Along with all the new property additions to the .lvclass file - this addition of a native ByRef scheme (for any datatype in LabVIEW) looks awesome. Plus NI have fixed up the conflicting file names get moved outside executable problem which usually comes up from using .lvclass files, (rather then .lvlib for me). Therefore, from my point of view, I couldn't have asked for more in a release, from what I have seen: 2009 is a great release for me, as it covers my biggest issues/concerns/problems/gripes that I was facing as a LabVIEW developer using LVOOP on PC targets. LVOOP moving to RT sounds sweet too. Also wrt ByRef LVOOP - I can't wait to see the examples the community comes up with. Cheers Kudos to NI, (and of course AQ) for their brilliant work