Downstream polymorphism example for Idea Exchange comment

Because I cannot put attachments on comments in the Idea Exchange, I am posting the VIs here and linking to this post from there.
This is for this idea.
Solved!
Go to Solution.
Attachments:
PolyVIClassSelector.zip ‏39 KB

I'm trying to actually implement this idea in LV 2012 SP1 and I'm getting an error which seems to specifically prevent me doing what I want to do.
"The property definition folder named "Events" overrides a property in a parent class, but the overriding property accessor VI in the child class has a different filename than the accessor VI in the parent class."
Well, yeah, that's what I want to do. The code provided by AQ works without error, but trying to reproduce a similar behaviour in my own code produces this error. I have also created static VIs which reside within the property folder, each with a different datatype and different name but with the same name property folder.
What am I doing wrong?
The property of interest in "Parent" and "Child" is "Events". Both of these VIs return different datatypes for each class. Both are static VIs (non-DD).
Oh, I think I see the big problem here.... The classes in AQs code are not inherited from each other (They are not parent and child). This ability only seems to work between "unrelated" classes. This is a major problem for me. I don't want an "Override" functionality, I just want it to behave as it does in AQs example.
Looks like I have to go back to maintaining polymorphic VIs....... Bah humbug.
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant

Similar Messages

This idea is too extreme for idea exchange

This idea was partly inspired by this one and is so far out there that I didn't want to post it on the idea exchange.
Can anyone from NI give me an idea if it would be possible to port LabVIEW and everything about it to Eclipse in time for LV2025? Don't get me wrong I really like LabVIEW but the UI definately shows how long it has been around.
If this is not TOO crazy then maybe I will suggest it over there.
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Make-Example-Finder-Resizable/idi-p/1440960
=====================
LabVIEW 2012

A lot of people think of Eclipse as a Java Integrated Development Environment. But it has become a cross platform IDE "for everything and nothing in particular". It is a BSDish license so that part is easy. There are all kinds of tools that use Eclipse that are graphical in nature such as database entity relationship models and UML tools.
The IDE is awesome.
=====================
LabVIEW 2012

Idea Exchange

While I agree that the board for Idea Exchange was badly in the need of some updates, I must say just shutting it down for 3 months or more Is Not a great idea. It was one of the few places to post something with some hope of seeing a Official response from Verizon.

More proof they could care less about their customers. The more receptive the other carriers are to their customers the more Verizon will lose.

Links to "idea exchange"? version 2.0

hi,on the forum home page (forums.verizon.com) today there is a link to the "idea exchange"......to see the bad link, scroll down below the "idea exchange update" message in the right column,and just above the "twitter feed" ....see the facebook ad?scroll right within that ad, the second ad is for idea exchange......is this intended behavior?wishing a good day to you all

did i mark this solved before i checked to see if it was fixed? i think i did! however, the ad w bad link is still there

Updated Process for the Ideas Exchange

Hey folks! Spotify Community team here.
If you've been around the Spotify Community for a while, you've probably noticed that we keep tabs on your suggestions for improving Spotify through our Idea Exchange.
In an effort to keep the Idea Exchange as organized and up-to-date as possible, we've changed the way Ideas are submitted. We've outlined the new process with a step-by-step guide below.
We hope that you continue submitting ideas to make Spotify even better. While we can't promise that we'll implement every idea that you submit, but we'll always do our best consider each one and provide updates wherever possible.
The guidelines:
Search for previously submitted ideas. Someone may have already submitted the same idea.
One idea per post. No double dipping.
Ensure the idea is implementable. Avoid posting general feedback or questions in the idea exchange--the more specific the idea the better.
Use an intuitive title.
Submitting a new idea:
1. Go to the Idea Submissions Board.
2. Click the New Idea button.
3. Enter an Idea Subject that includes one of the tags above.
4. In the Body enter a detailed description of your idea, including any screenshots or links you'd like to share.
5. Select one a platform label.
6. Then select a subcategory label.
7. Click Post.
8. One of our Idea Guardians in the Rock Star Program will analyze the idea and mark it either as a "Live Idea" or close it for a specified reason (duplicate idea, unspecified, etc). Allow us to introduce our Idea Guardians: Marco, FredJ, gprocess, Peter, dinomight, Anthony, pnc, Jordi, kbrooksc, Carina, OviiiOne, and Rodrigo.
9. If your idea reaches the Live Idea board it can then start to gain kudos and comments from other users.
10. Once your idea reaches 100+ kudos a Community Manager or Moderator will update the status to one of the following:
The Idea statuses:
New Suggestion (no status/default one): the idea was just posted, it is waiting to be reviewed by an Idea Guardian.
New Idea: this is a new and unique idea, you can add your kudos here.
Inactive Idea: Ideas that could not gather at least 25 kudos per year will get closed - you can submit this idea again if you still feel the topic should get some attention. We recommend changing the title or description if posting the same idea again.
Good Idea, give it some kudos: We like this idea. A decision has not been made but we want to see how much the Community continues to vote on it.
Under Consideration: This has been brought up internally.
Watch this space: This feature is coming. We have a rough pipeline for its release.
Not right now: We talked about this internally and it’s not on our pipeline for the next few months or more.
Case Closed: We talked about it, but we won’t be running with it. Thanks anyway!
Implemented: This feature has rolled out on the specific platform.
Needs more info: We need more clarity or information around this idea from the original poster.
Curious for more information about the Ideas Board? Check out The Ideas Board: How your feedback reaches Spotify.
Thanks for your continued feedback and contributions everyone,
The Spotify Community Team

Ah, yes, now I see it. For those of us with less than perfect vision, how about putting the text in red in the center of the page as opposed to in only slightly darker green to the right. I've never used this page before so I had no idea there even was something to select on the right hand side. Also, the first link in the first post on this page gives me this: "You do not have sufficient privileges for this resource or its parent to perform this action.Click your browser's Back button to continue.Return to my original page"

24 Great Ideas from Idea Exchange for you to Kudos

There are 1140 ideas on the LabVIEW Idea Exchange right now. That's a lot of ideas, and it doesn't even count the RT or FPGA exchanges. Reading through all of them is something most of you can't spend time doing. Some of the ideas quickly garner a lot of Kudos, and those jump to the top of the lists and get attention from NI. Others are good, but they languish, lost in the noise.
I have read them all, generally by staying up-to-date on the forum ever since its inception. I kudos'd many as I went. Over the weekend, I went through all of the ideas I had kudos'd and picked out a set that I think a lot of customers would want but that don't have the high Kudos ratings. Maybe these got posted on a weekend or holiday. Maybe the title is a bit misleading and you didn't bother to read it. Or maybe you've just stopped reading the Idea Exchange because you couldn't keep up with the wash of words fellow wire workers are writing. Perhaps this simplified menu will be a bit easier to browse.
To be clear: I'm not including any of the ideas that already have high Kudos counts. Those are great ideas, but they've already got their time in the sun. These are the little quiet ideas that I think might make a big impact on your productivity, your VI's functionality or your VIs performance. All of these had fewer than 100 Kudos when I made this list. Full disclosure: Two ideas on the list (12 & 23) are ones I submitted to the Exchange. I think they warrant being on the list, but maybe I'm biased because they happen to affect the areas of LV I use most. You be the judge... :-)
User-defined partial Highlight Execution (so you only slow down execution in the "interesting" part ...
Simpler Array Size (shows N terminals where N is the number of array dimensions instead of a single ...
Conditional auto-indexing for output arrays (for when you need to filter an array down to just the s...
(and I should also mention its companion idea, although this one has 102 Kudos: Add a Concatenate Indexing option for arrays leaving For Loops
Right-Click on FP Terminal to add Event case for that control
Make "TypeDef" the default choice in the control editor
Make-mouse-wheel-scroll-the-string-control-indicator (and other things that should recognize scroll ...
Adding a "don't wait until done" option to the Call By Ref node
CTRL-Double-Click on a VI in project windows should open Block Diagram directly
Scroll-Bar-Property-for-Clusters
(10 and 11 go together) "Create-SubVI" or "New V" DEFAULT VI Template
(10 and 11 go together) Create a proper connector pane when doing Edit >> Create SubVI
Tag an XControl as the default control or indicator for a LabVIEW Class (so we can finally build new...
Add a "Mouse Scroll" event
Add a Click Event (so we can stop checking for Mouse Down followed quickly by Mouse Up and just let ...
Make-project-window-dockable-and-always-on-top
Separate-label-locations-for-Controls-and-Indicators
Add symbol on string control/constant to tell when string is in slash or binary or password display ...
Add a new debug stepping button: "Finish SubVI And Close Panel" (helps to avoid panels littered all ...
Be able to Find All Instances of VI and view VI Properties when the VI is in run mode
Bad-wire-gets-cleared-automatically-when-it-can (as the idea says, hard to explain, just look at the...
Allow-vertical-scrollbar-on-arrays-with-1-visible-element (and, I'll go further and say vertical, no...
I-would-like-to-see-a-Close-Other-VI-s-option-in-the-File-Menu
Shift-Enter-should-define-word-wrap-bounds-on-Free-Labels (just like it currently does for string co...
Insert "In-Place Element structure" onto wire
There you go... 1140 down to 24. If you've got other aspects of LV you'd like to see improved, add them to the Idea Exchange.
Solved!
Go to Solution.

Mads wrote:
A good example is the fact that one of the most popular ideas ever was the idea to adjust the design of the boolean constant. Altenbach, who came up with that idea, have received less kudos for other ideas that I'm sure would give him (and us) much higher benefits. Popularity and greatness are very often two different things.
Although I get your general point, having used LV 2010 in beta for the last few months, the improvement of readability of diagrams brought by the boolean constant change cannot be understated. Tons of VIs have arrays of boolean constants on them, have boolean constants squeezed into small corners, etc, and the redesign has helped A LOT.
Speaking to your general point -- my goal was to find low-ranked ideas that I felt would have significant developer impact and give people a second chance to review those ideas. Are there other ideas among the 1000 that are worth doing? Sure. I tried to find a broad enough set that people could actually make a meaningful choice of what to kudos (any fewer and it would be akin to "hey, everyone, come vote for this particular idea"). And it does rely upon my opinion -- though I tried to use my professional opinion as someone who regularly hears user feedback to promote ideas that I think users would generally like, as opposed to my personal opinion as a LV developer to improve the areas of LV that I personally use a lot.
I know that customers like it when NI is responsive to its demands. I know that NI knows this and so is proactively trying to address concerns that make it high on the Idea Exchange. LV 2010 is coming out in August. If you look at the ideas that are tagged "In Beta", you can see the responsiveness of NI. As we start work on the next version of LV (or rather, full time work, since future versions of LV are always already in work -- we are a parallel language in so many ways), we're going to go find the next batch of ideas to implement. But I also know that there can be user fatigue with the Idea Exchange's massive amount of content. That fatigue can lead to a strange situation where NI addresses the high flying concerns and, users are still left feeling they didn't quite get what they wanted, but they maybe can't say why because, after all, NI implemented the high kudos ideas. I cherry picked some ideas that, if implemented, I think would get a lot of people saying, "Yes, LV is now better" as a way of avoiding some of that fatigue effect. Is it a list of earthshattering ideas that revolutionize LV? No. It is a list of incremental improvements that should affect lots of people and make LV recognizably better to its users.

Idea Exchange for Forums

The Idea Exchanges seem like a great way for NI to judge customers' sentiment and importance of feature requests for LabVIEW. It provides a formalized and centralized means exclusively for improving NI products and services. I presume it also is a factor in budgeting resources for R&D.
I would propose an Idea Exchange be made for the forums as well. This forum (the Feedback on NI Discussion Forums) has got great little tidbits scattered throughout on features that would make these forums AWESOME (not to mention all the tidbits scattered throughout other forums). The problem is that those tidbits are buried in so many places that it would be extremely difficult to centralize them into one list, and it would be impossible to prioritize the ideas. The other problem is that since the ideas are so scattered, the number of people who would read them and say "YES! I want to see that too!" is dramatically reduced (compare readership of this current Feedback forum to that of other forums - it just doesn't get the same exposure).
Basically, it's unfair for me and others to continually make snarky comments here and there about how the forums suck and Lithium doesn't know squat about web development or user interfaces. It would be much more beneficial for the us the community and for the developers/maintainers of these forums if we could get some structured, formalized feedback on how to make the forums better through the use of an Idea Exchange. This would provide sufficient, constructive means for people like me to vent frustration about bugs and features that I want in upcoming forum upgrades. (I'm here because I like the forums, not because I want to gripe about the forums!)
One important benefit for both NI and the community that an Idea Exchange would offer is that we all can see loads of these Ideas being marked as "Completed" when forum upgrades are implemented. It feels good to see our feedback is being heard and knowing we have worked together to make a better product/service. If we don't see a list of "Completed" features and bugs, it will be all too easy to focus negative attention on the new bugs.
(I am aware the current process is such: one of us makes a suggestion here or there, and then Laura makes an Idea on the actual Lithium Idea Exchange. She's really diligent about this, but the problem with that process is that it's not our community that prioritizes the features we request, it's Laura's peers on that other forum who decide if our Ideas are worth implementing or not. I think it should be the LabVIEW community that prioritizes feature requests, and then Delegate Laura and Delegate Todd are able to go to Lithium directly with their constituents' priorities. I mean, it's not even worth bugging Lithium about a feature if nobody but the creator likes it!)
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Laura F. wrote:
I actually talked to a contact at Lithium recently about our forum users voting on the Idea Exchange and it seemed like it would be fine. If you want to register and vote on ideas that I've submitted on your behalf, please do so. You could also submit new ideas, but they may get more visibility if I submit them as I am a known user / customer of the platform. I'm convinced there's not enough crowd momentum of LabVIEW forum users who would invest the time to make this venture worthwhile. Also, based on your comment below, I realize I'm not qualified to do this.
One problem I also see with our users submitting ideas directly is that sometimes the idea has to do with a feature of the Lithium platform that we don't have turned on. That just means that I can provide some insight into whether or not your idea falls into this category prior to submitting the idea to Lithium. See next comment...
I am open to creating an Idea Exchange for the forums themselves. Neat! This would solve your comment above. An internal Idea Exchange would help you prioritize which components/widgets to turn off/on without bothering Lithium with potentially moot requests. Some of your suggestions are things that are not directly tied to improvements in Lithium's software but rather to how NI has chosen to implement the forums. Those sorts of ideas we have control over. I am solely responsible for the features on the forums now, Neat! I hope it came with a pay raise so it may take some time for me to implement some ideas but I would be willing to give it a shot. We would need to keep the Feedback board for bug reports and other more support focused questions. Agreed, an Idea Exchange is not a replacement for the Feedback Forum. The Idea Exchange should not be used for "day to day" maintenance such as broken links, that's what this forum is for.
However, my first priority is getting the forums upgraded what's your expected launch date... days, weeks...? This forum upgrade I would like to see the Idea Exchange upgraded a few weeks before NIWeek so we can test-drive it a little while, because like last year, we're going to see a little surge on the Exchange after NIWeek. so that you can see the new version because some ideas and bugs are addressed. And then, we will start on a new list of ideas and bugs
I appreciate all of the time and effort all of you put in to make the forums better for everyone AND all of the questions that you answer throughout the community. I look forward to continuing to work with you all on improvements.
Regards, My reciprocate regards
Laura
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Looking for examples of the Exchange Page

Hey! Any Body??
I am looking to display data like on the Exchange page with
logo and links in the tables. Does any one know of where I can
start looking for something like that? I like the layout of the
Exchange page. If any of you know something please let me know.
thanks.

You can find several examples that will work with the DAQCard-1200 at zone.ni.com/libraries/.
Then look under Data Acquisition. There are also examples that ship with
LV and NIDAQ. Look in ...\Labview\examples\daq\anlogin\.
"david frazao" wrote:
>Thank you , if you can help me by sending VI examples for the 1200 daq-card>,
with 2 or mores inputs>>

Picture in a Comment on the LabVIEW Idea Exchange

How do you post a picture in a Comment on the LabVIEW Idea Exchange?
Richard
Solved!
Go to Solution.

altenbach wrote:
Broken Arrow wrote:
How do you post a picture in a Comment on the LabVIEW Idea Exchange?
Submit the comment without picture, the edit it.
Once you edit the comment, you have the full editor, including the "attach" button.
Now attach the image and submit the edited comment.
Now edit it again and embed the attachment (you only see it whe editing).
Do all this quickly so you don't run out of time.
Laura,
Since the last forum update, we can no longer attach anything when editing an idea so these instructions are no longer valid. Can we have the old functionality back? Please?
Thanks!
LabVIEW Champion . Do more with less code and in less time .

Better search/indexing capability for the Idea Exchange Forums

Now that we are getting more ideas posted to the idea exchange it would be helpful if we could have an improved indexing and search capability. This would help to reduce the number of duplicate ideas posted. I know I have ended up posting a couple of duplicates even after searching.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

If you ever have a specific example of the search not finding a related idea, please post it here. When I've gotten feedback about this before and then tried to search myself, it seemed like the related idea always came up. I definitely would like a specific case that I could give to our forum vendor.
I do agree, the Google like feature with misspelled words would be very helpful and I'll pass along that suggestion.
Thanks!
Laura

Change 'Kudos' to 'Votes' on the idea exchange

Sometime I discuss an idea on another platform than the NI forum (Info-LabVIEW, LAVA, real life) and I advise them to vote for a particular idea on the Idea Exchange. For people foreign to the 'Kudos' term it's sounds strange, while calling it 'Votes' makes it more recognizable.
Kudo is a term mainly used on internet and in youth communities, it might be astranging to more serious programmers.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

A use case is found here, where David Ferster made his first post in 8 years to give me moral support after I pointed him to the idea on Info-LabVIEW. What he should have done is make a Kudo to the idea, but being new to the community he didn't knew what to do and did the most natural thing people do on a forum: they post.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Idea Exchange - Show Random Old Ideas?

There really are a lot of ideas now on the exchange. I think that some really good ideas get buried in the stack before some of us get a chance to see them.
Maybe it would be useful if there were a section under Active called "Random" or something that would show a page of random ideas. There probably should be some filters/rules such as it needs at least one kudos, has been viewed under a certain number of times in the last week, is at least n weeks old, is not currently listed in another Active section, etc.
A lot of Wikis have a feature that will show a random page. Just a thought.
=====================
LabVIEW 2012

I think that's an excellent idea. I know I've seen all the ideas because I went and read them all while the list was still small, and have kept up on reading all the new ideas and comments as they've come in. I think if anybody started following and reading through them now, it would be overwhelming because the list as grown so dramatically. I think there are a lot of ideas out there that have low kudo totals that should naturally be higher, but it is because they are old enough that the only people who had seen them have been following for a long time. I think that is why you see a number of duplicate ideas as well. A good idea comes up again, but the original new idea is long buried, and the new idea person either fails to search, or the search mechanism fails them in trying to find whether the idea already exists.

Idea Exchange enhancements

In this exchange:
Need a new label - Idea Exchange - for improvements to this forum
Add "Previous/Next" at the top of each page as well as the bottom.
Add "To First" and "To Last" as well. Do it like other forums where you can jump to a specific page or to the start or end.
Allow me to search for the date, and put me in the chronological LIST of ideas at that date. Currently you can search for a date, but it gives you a list of ideas from that date and you can only go to the idea and its comments. I keep track of the last date I checked the list and would like to jump to that date IN THE LIST.

Hi Roy,
One workaround to finding ideas you have not read is to use an RSS feed for new ideas as tst does, or to click on the "New Ideas" tab - the newest ideas will be at the top and you can work your way down to the idea that you have last read.
I will submit your suggestion about jumping into the list at a particular date. We have already submitted the suggestions about navigating between pages.
Thanks,
Laura
Web Support & Operations
National Instruments

View New Posts in Idea Exchange

Is it possible to add a feature to View the latest messages posted onto the LabVIEW Idea Exchange. The ability to sort by last message would suffice. I like to follow the discussions, but sometimes I see there's a new message, but I have to click through 40 pages to find which topic the reply was posted to.
Tim Elsey
LabVIEW 2010, 2012
Certified LabVIEW Architect

Yes. That is pretty much the only way right now to be sure you get all the messages. Occasionally, I can still miss some. For instance, if I have an e-mail that I thought I clicked on and read the idea linked in it, but actually haven't. Or the way the long threads that go onto multiple pages, and I miss the last message that rolls onto a new page and I didn't realize it because the link to go to the next page is at the top of the screen. (And why don't the messages show you that 5 pages are avaible to that thread.) You can see a count of total messages. But it will show you Now 1-10, and a link to go to 11-21. But there is no link to go to the last page. You have to go through the pages one by to get the link to the following page.
The naviagation controls in the individual threads need major improvement. (i.e. jump links at the bottom as well as the top, and links that go to other places then the page that just follows your current page.) And the whole board needs a real sorting mechanism that allows you to view the newest messages whether they are the original message or comments. The "snapshot" links to the right of the screen just really don't do that.

Diadem idea exchange

Every once in a while I check the idea exchange for Diadem. I think that several of the ideas are good. The forum has been around a while including time spans when there was a new release of Diadem.
However, all of the ideas are marked as new. Why aren't some "in development"?
Does the development team give any consideration of the ideas? Even the decision that we won't do it would be appreciated.
Jim West

Hello Jim,
Please rest assured that the DIAdem sales, marketing and especially the R&D team are monitoring the DIAdem ideas forum closely. Several of the ideas listed there have made it into DIAdem 2011 (you can check out the BETA version of 2011 at http://www.ni.com/beta) and several others are on the preliminary list for DIAdem 2012.
We may not be doing a great job on tagging these as "in development", but we are certainly paying close attention to the ideas and feedback from other users on specific ideas. Comments and "Kudos" given to ideas on that forum will help us to determine how many people are interested in a specific feature, so we encourage everyone to make use of both the "Kudos" and the comment function there.
Thank you for your feedback and for bringing this important development tool back into focus for our users as well as the NI DIAdem team.
Otmar
Otmar D. Foehner
Business Development Manager
DIAdem and Test Data Management
National Instruments
Austin, TX - USA
"For an optimist the glass is half full, for a pessimist it's half empty, and for an engineer is twice bigger than necessary."

Downstream polymorphism example for Idea Exchange comment

Similar Messages

Maybe you are looking for