Leaderboard

Here's another reason I don't visit IE very much: There are 1400+ ideas, and only 1 is "In Development". There are 20+ ideas with over 150 kudos. All marked "New". Most over a year old. So there doesn't seem to be a lot of point in submitting ideas or voting on them. Yes, I know 10 or so ideas were implimented in LV2010. But that left a whole lot of ideas with a whole lot of user support behind. In reality, I can't image the LV user base is really being ignored like this. Maybe the "Status" field needs to be updated more often? Or maybe there need to be more options than just "In Development" and "Being Ignored" "New"? Maybe "Under Consideration"? "Not in a Million Years"? Just more feedback, and updated more often, as to whether or not NI is actually paying attention to what gets posted in IE.

This is definitely not a better way to do but maybe a workaround to try (I've implemented this solution in this XControl): Create an hidden cluster with a string and a variant in your facade VI Create an event case on Cluster "Value change" Give cluster reference to your parallel process Do "Value (signaling)" using the cluster reference to "fire event" Process action in the event case create in 2. String and variant allows you to implement multiple action and different data to process in your facade VI. Hope this can work for you. Regards Olivier

How about this?

Try one of these.

I'd say no.. My basic motto is: don't close what you didn't explicitly open. The owning VI is still in memory, even after this call to the facade finishes, so a close will probably be a nop. The one responsible for actually closing the ref (and thus cleaning up the VI object) is it's initial creator, a specific application instance. The one thing that's left is the memory location that holds the refnum (pointer to the VI object) and that should be taken care of by the garbage collector as it is for all wires that at some point on the diagram stop and their value is of nu use anymore. 100% sure? I sure hope to be close, otherwise I'm going to have to file a bug report.

Thanks for the link to the feed. I did not find it myself. It is hidden in the menu "Idea Exchange Options" (above the first idea). There is also an entry for subscribing (getting an email). Some other existing things that can be used: tagging: follow the tags and tag the ideas yourself labels: There are some labels defined. When one is your main interest follow this one. (If you would like more different labels, kudo here.) kudos of others: When someone has the same LabVIEW taste as you, follow his kudos ("Messages I Recently Kudoed" on his page) ideas of others: When somebody has good ideas, check those he sent ("Recent Posts by x" on page of x) ... Greetings, shb

I would very much be against this. I try to follow every post on the IE and if there was a bunch of ideas which all appeared together it would simply flood me at that point in time instead of allowing me to go at my own pace. I would agree that the problem is probably because people don't follow the exchange, but the solution to that might be to make it more accessible. For example, the IE has an RSS feed for ideas, just like Shaun asked for - http://forums.ni.com...id=labviewideas The problem is that if you don't look for it, you don't know it's there. The site doesn't seem to make it accessible enough. Ideally, it should provide people with several ways of getting alerts to either ideas or comments. In any case, I think that people have to make a conscious choice to follow the exchange or they will have to rely as filters such as this thread to point them to specific ideas.

It takes balls of steel to release a LabVIEW toolkit product and I commend SAPHIR for stepping up to the plate. Having gone down that road, I can tell you it's not something any company should or can take lightly. I'll eagerly wait for a trial version and will provide any feedback I can to help test and improve the product.

I have alway set these in my INI file: appFont="0" 13 dialogFont="2" 13 systemFont="1" 13 HideRootWindow=True blinkBG=000000FF thanks for the font info. I guess I will need to find a way to detect the OS and go from there.