Leaderboard

I have a proposition for a new LAVA 2.0 top banner. Because you liked my design for t-shirt, I modyfied it a little bit to suit it better for horizontal orientation. It looks like this: It is suited rather for light background (just like block diagrams are), but I can think of modyfing it for dark ones. For blue or dark blue also some colors should change. What do you think?

So after some cleaning up (which in this case means few hours of work beside repairing broken code ) I can put on the table what I have. The main file is VIpreVIEW.vi. You have to open it, fill all paths, sizes, etc. and run (not very professional, isn't it?). After some work (depending on VI complexity) it will create a lot of files at target path. Most of them are temporary files, but I do not delete them yet for debug purposes. Open {name}.html file in a browser and watch the result. I included SWFtools binary in this package (it's GPL) but I don't know how it is with all that legal stuff. Know issues: it is sloooow sometimes it is even slooooower additional 1px black line appears at each case (it is not an issue in alternative flash players as Gnash) tips appear even for objects in hidden cases (still don't know how to solve this) tips appear for each object (even not necessary, like comments) and often display sth stupid - this is for debug did I mention it is slow? many others Any comments are welcome, particularly if someone has an idea how to speed it up a little. I already tried to convert it to non-recursive version. Although I had some problems, it seems that recursion is not the reason. I think now that a bottleneck is speed of switching cases externally. If it is true, the stack version of algorithm should work even slower. And of course GUI in final version will not look like this. [moderator note] Attachments to this post are missing due to server error. We apologize for the trouble.

Not that I know of, that's how I would have done it.

You didn't see the data for D change... and *that's* the problem. ;-)Let's take a simple case: Class A has a private field "numeric" (default value 0)Class B inherits from A and has a private field "numeric2". (default value 0)Class C inherits from B and has a private field "numeric3". (default value 0)Class A implements a static dispatch VI "Get Numeric.vi" that returns the value of its private numeric field.Class A implements a dynamic dispatch VI "Increment.vi" that unbundles Numeric, adds 1, and bundles it back into the object.Class B overrides "Increment.vi" to unbundle Numeric2, add 1, and bundle it back into the object. Then it invokes the Call Parent Method.Class C overrides "Increment.vi" to unbundle Numeric3, add 1, and bundle it back into the object. It DOES NOT invoke Call Parent Method. What happens when we call "Increment.vi" and then call "Get Numeric.vi"? If the object is of type A, we dispatch to A:Increment.vi, and Get Numeric.vi returns 1.If the object is of type B, we dispatch to B:Increment.vi, call up to A:Increment.vi and Get Numeric.vi returns 1.If the object is of type C, we dispatch to C:Increment.vi, and Get Numeric.vi returns 0. Would you agree with me that any time I call "Get Numeric.vi" on a C object that I should get zero as the answer? Since C has overridden Increment, there's no other way for that field to be modified. So one of the invariants of C objects is that Get Numeric always returns zero. Now, what happens if, on the diagram of B:Increment.vi, we wire a C object directly to the Call Parent Method node? When we call "Get Numeric.vi" on that C object, we get the answer "1". That violates one of the invariants of C objects. The defined interface of the class is broken. And that's a problem.

Context help for the LAVA icon: LAVA Icon with Wires.vi

I like the new version in the banner (see below), but I think it'd be better with the red and blue wires coming out the bottom.

Sure, the following code will do what you want. As I understand if 1A or 2A exist in a comma separated string then light up 1A or 2A if exists.

There are two ways to do this. 1) Create a measurement task in MAX where you specify the temperature range and other parameters of your measurement and then in LabVIEW perform acquisition using that task. 2) Basically create the task in LabVIEW by using DAQmx Create Channel where you can specify the range of your measurement. I believe in your case you are calling DAQmx Create Channel (AI-Temperature Thermocouple).vi where you do specify the limits and also thermocouple type, cjc source ect so for your case you dont need to jump into MAX to set anything up.

Use the Type Cast primitive to cast your strings to an array of uInt8. Then you can compare each element.

Hi Jim, You can use the Visible Frame property, as shown below: Cheers, -Jim

I just wanted to inform that after total rewrite of everything (to LVOOP) I reached exactly the same functionality as it was before. That's a progress, isn't it? So now it's time to start extending VIpreVIEW. For the beginning, following Yair's suggestions, I designed a logo: I also attached recently generated swf, as these from previous posts are gone, but I'dont know how to embed it in the post... BBcode is not working. test3.swf Also if someone who got the power could move this topic to uncertified code repository where is much better place for it?

I see there are some new options for "Voting a post up" and giving a star rating to a thread. Each user also has a "reputation" count. How are these things tied together? The reputation appears to be tied to the number of votes a member receives on his/her posts. Does the star rating also contribute to reputation? Gone are the days of making many useless posts to make myself appear useful. -Toby Edit: On a side note...I am able to give a star rating to my own post. That seems odd to me.

After a year of doing something from time to time, investigating various flash generation libraries and turning whole the code up side down, we have another prerelease of VIpreVIEW (interactive preview of VI in flash). Visually almost anything was not changed and actually even code looks similar as in previous version (best ideas come at beginning), but: it is much faster (speed is already reasonable) flat sequence works (however it is implemented pretty ugly) fixed issue with showing labels from not visible frames fixed issue with additional 1 px border its is much faster (repeating this because I'm so proud of it) and what even better - it still may be faster (and I know more or less how to do it) Below some instructions copied from the first post: The main file is VIpreVIEW.vi. You have to open it, fill all paths, sizes, etc. and run (not very professional, isn't it?). After some work (depending on VI complexity) it will create a lot of files at target path. Most of them are temporary files, but I do not delete them yet for debug purposes. Open {name}.html file in a browser and watch the result. I included SWFtools binary in this package (it's GPL). Comments as always are welcome