Yair

The second feature there is great. The forums style view of the list has been annoying me and this makes the behavior the same as it was in the old site. Actually, regarding the second option, it has two problems: The first is that the terms it uses are technically correct, but the "forums style" is the one which is actually more like a list. But that's just a semantic issue. The bigger problem is that in the forums style view, you don't get the alternating colors for each line. I think this is a bug.

So, where's the new code? P.S. Great logo, but you should probably flip it, so that it looks more like the LV logo.

That's a common misconception. If you poll the queues with a timeout of 5 ms (or even 1 usually), your CPU consumption would usually not be high and you would get the data quickly (ASAP is a relative term). This of course depends on many factors, but I'm speaking generally. That said, the other suggestion is better.

I already reported it to NI in the past (CAR 160091). It appears in the beta pages as deferred (who knows until when. It's not exactly a critical issue).

I'm assuming you're refering to the main page. You need to click the unread content link under the search box to get to all the new posts.

If you don't mind polling, you can just have a subVI which will get an array of queues and iterate over them in a for loop until it doesn't get a timeout.

Click Shift+Enter when you get to the end of the area and the string constant will become a multi-line string. Unfortunately, that doesn't work with comments, where it's much more commonly needed.

I definitely agree. I leave it on and think it's very important. Another way of handling something like this is by running the relevant VI analyzer test (assuming you have VI analyzer, of course, and are willing to only find something like this retroactively). I actually like your idea of highlighting such a structure somehow. You should probably suggest it in NI's idea exchange.

Which code? What I'm talking about is something that NI has to do. A direct replacement for the error cluster. And yes, I'm aware they're not going to do anything about it soon.

Also, there's one here.

I posted an example here showing how it's done. It's not there right now, so I'll tell Michael about it and he can fix the link. If memory serves, you can add separator lines by adding an element whose text is "-".

I would agree with the Error class way, but it should be a collection of errors. LV is parallel - we need a way to merge errors into a single wire without losing information. Once you do that, you can have the base error class with the items Chris suggested, but add specific data for specific error handlers (thus there's no need for the custom properties variant). It would be great (actually, it would probably be a basic requirement) if LV was smart enough to coerce error wires into such an object, so that we have backward compatibility.

You're right. Go and vote this idea up and hopefully NI will implement it. There are actually a couple of other copies of that idea that people posted, but they all boil down to the same thing.

Thanks, definitely better.

OK, I guess it is 1996. I was hoping Invision would improve their search with new versions, so I wouldn't have to use Google any more.

It works differently for boys.

I'm assuming it uses the linker methods which read the info from the binary data of the VI without loading it into memory. I was more concerned about the performance if you have a large number of small classes (since each would probably have only two methods) and about the ease of use of loading them dynamically. In any case, it's kind of theoretical, since I'm planning on doing anything like that at the moment.

You should post this to NI's idea exchange (although I'm pretty sure this was already suggested, so you should search for the original and vote it up).

Why, oh why, doesn't the search box AND the search terms I put into it? I thought the entire world would have figured by now that this should be the default option for every search. In fact, I can't seem to find a way to AND search terms at all. Luckily, Google allows searching a specific domain. Let's hope it already indexed all the new pages on LAVA.

There are some VIs in this thread. Note that the scaling they do is dumb, so don't expect great quality. Also, the one posted near the end can be simplified somewhat. Note - the palette has VIs for converting from the picture wire to a 2D array and back.

Congratulations, Stephen. It would certainly be useful to see a relevant example, maybe based on one of the sample exams. It would not be unreasonable to assume that NI is already working on this.

The FP.Is Frontmost property might be able to help you, but will mean that you have to cycle through the different FPs, which will probably be visible to the user as it happens.

Is there any chance of not having it visible unless it actually has some content in it? I promise to try and behave and as long as it's empty, it's annoying visual noise.

Here's an example of this sort of thing. I'm assuming the classes there are more complex than what I'm thinking about, but we can't know unless Daklu steps in. In any case, this is exactly the sort of thing I'm concerned about.

The pages area is hard to make out if you're not aware that there are multiple pages. It should stand out more.