Diuplicate posts on the NI TestStand Idea Exchange

Hi Laura,
How do we get duplicates posts removed from the NI TestStand Idea Exchange.
Regards
Ray Farmer

Laura,
I thought there must have been an Option menu but couldn't initiately find it hence my post. But I have located now and notified of the duplicate.
regards
Ray
Regards
Ray Farmer

Similar Messages

  • Support the launch of an NI TestStand Idea Exchange!

    Calling all TestStand users!
    While I love TestStand, I've got some ideas on how it could be improved, and I'm sure you do too.  NI recently launched a new platform for getting and tracking ideas on how to improve thier products called the NI Idea Exchange.  If you haven't seen what it's about, see the intro video here and then have a wander through the wildly successful LabVIEW Idea Exchange here.
    There's already a LabVIEW Idea Exchange, a LabVIEW RT Idea Exchange and a LabVIEW FPGA Idea Exchange, so why not a TestStand Idea Exchange?  Well, setting it up and supporting it takes time and resources, so, we need to let NI know that we think having one is worthwhile.  If you're interested in furthering the development of TestStand, you need to let NI know that you're interested in a TestStand Idea Exchange!  If the idea of a TestStand Idea Exchange appeals to you, please post here to show your support.
    Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.
    Solved!
    Go to Solution.

    Great idea!

  • Why is the Real-Time Idea Exchange completely ignored?

    Just looked at the LabVIEW Real-Time Idea Exchange and noticed that only one idea is marked completed, and two more (both posted in 2009, nearly 5 years ago) are "In Development." Those ideas aren't even the top-kudoed ones. NI - why ask for ideas for improvements, and then not implement any of them? (Yes, I have a personal interest here - the second-most kudoed idea in the real-time area is one of mine.)

    First off let me say thanks to you and all of the Idea Exchange contributors. The whole purpose of the Idea Exchange is for you, the users of the NI Platform, to bring your considerable experience to the table as we continue adding features and functionality to the NI Platform. Your passion is one of the primary forces that causes the NI Platform to grow and change in varous ways so that the application challenges of scientists and engineers all over the world can be solved.
    There are many user suggestions across the whole Idea Exchange for us to weigh when considering how to allocate our development resources. We try to judiciously consider which ideas will have the biggest impact on the NI Platform users, and as a result we often have to say "no" or "wait" to some ideas so we can say "yes" to others. You're definitely correct that the statuses need to be updated and I'll be doing so in the near future. Though this may give the impression of being ignored, I want to assure you that the ideas are read and evaluated by the R&D and Product Marketing departments with careful thought and deliberate intent.
    We hope that events such as NIWeek bolster your confidence in the progress of the NI Platform as you see the new hardware and software features being introduced. Though you may not see an immeadiate reward for your dilligence in suggesting ideas, please continue submitting your ideas. The long term effect will be a powerful platform of products designed to meet the community's needs. Thank you for your continued support and engagement.
    Deborah Y.
    LabVIEW Real-Time Product Marketing Manager
    Certified LabVIEW Architect
    National Instruments

  • LabWindows/CVI Idea Exchange

    National Instruments introduced the LabWindows/CVI Idea Exchange for submitting and voting on feature requests to be included in future versions of LabWindows/CVI.
    The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange, so start posting your ideas today!
    Adri Kruger
    National Instruments
    LabVIEW Product Marketing

    One of the more valuable tools within LabWindows is the ability of the editor to fill in struct elements given the struct name. I also work with Eclipse-based tools for embedded systems work, and it has a similar ability. Unfortunately, whereas Eclipse dynamically analyzes the code as it is written, and can provide stuct elements (and other variable information) as soon as the programmer types it in, LabWindows cannot provide this information until after the code has been successfully compiled. As this may or may not happen for some time after the file has been started, or major changes begun, it is almost useless.
    Another useful tool that Eclipse offers that LabWindows does not is the ability to refactor variables and other symbols. Again, Eclipse dynamically tracks the code as it is written, not requiring compilation; refactoring is similar to global replace, except that it tracks the 'C' usage of the symbol and only changes the proper usage. So, for instance, if I use a local variable named "X1" in three different subroutines, and refactor "X1" to "X2" in one of them, only the variable in the particular routine gets changed.It works with any C symbol, including routine names, global and static variables, and structures.
    As a matter of fact, I would encourage NI to look into the possiblity of basing LabWindows on the Eclipse platform, as Atmel did in replacing its proprietary Studio software with an Eclipsed-based version. This would enable users to take advantage of a large number of available Eclipse tools, such as source-code management.

  • NEW! Measuremen​t Studio Idea Exchange

    Do you use Measurement Studio regularly? Would you like to influenece future releases of the product?
    National Instruments introduced the Measurement Studio Idea Exchange for submitting and voting on feature requests to be included in future versions of Measurement Studio. This is the most direct route of communication with the Measurement Studio R&D team and we are committed to reviewing every idea submitted via the Measurement Studio Idea Exchange, so start posting your ideas today!
    Anna Kozminski
    Measurement Studio Product Manager
    National Instruments

    为什么装不了呢啊~!

  • Measuremen​t Studio Idea Exchange

    Do you use Measurement Studio regularly? Would you like to influenece future releases of the product?
    National Instruments introduced the Measurement Studio Idea Exchange for submitting and voting on feature requests to be included in future versions of Measurement Studio. This is the most direct route of communication with the Measurement Studio R&D team and we are committed to reviewing every idea submitted via the Measurement Studio Idea Exchange, so start posting your ideas today!
    Anna Kozminski
    Measurement Studio Product Manager
    National Instruments

    Above links is broken. Here is the proper link to the Measurement Studio Idea Exchange.
    National Instruments

  • 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.

  • 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;}

  • Memory usage of big Array in sub-VI (was: Allow the creation of "Inplace"-VIs of Idea Exchange)

    Hi,
    this thread is based on my post in the LabVIEW idea exchange.
    I put my VIs in the attached .rar file.
    Regards
    Marc
    CLD
    Solved!
    Go to Solution.
    Attachments:
    Inplace_VI.ZIP ‏21 KB

    That would be a good explanation.  There was a thread on something very similar to this recently.  Can't remember exactly the topic but Daniel's answer certainly triggered some memories of a very similar discussion taking place.
    I think it had to do with LV assigning a Array created as a constant as Read-only so in order to make changes to it it needs to be copied to a new memory location, thus leaving the constant unchanged.
    I wonder how it performs in other LV versions.
    Shane.
    PS: Found the thread.  HERE.
    Message Edited by Intaris on 08-20-2009 03:23 AM
    Say hello to my little friend.
    RFC 2323 FHE-Compliant

  • Problem switching from a non Idea Exchange board to an Idea Exchange board when typing a new post

    Tested on Chrome/XP and IE8/XP
    when I start a post in a non Idea Exchange forum and later on want to convert it into an Idea Exchange one, I can switch to the correct forum using the "Select Board" pull-down list. However, when posting, my post is refused because I haven't chosen a "Label". Well, that's because I can't!
    In other words, switching to an Idea Exchange board does not add the "Label" options on the composition webpage, hence it is impossible to post that idea unless you copy it (or rely on the autosave function), start a new post directly into a Idea Exchange forum and paste your old post in it (or alternatively, load the saved draft once you have created the new post).
    Disclaimer: this may have already reported, but as I said elsewhere, the Search function doesn't work either...

    This is my first post so be gentle with me.  I have a Pixi Plus running os 1.4.5.  Last week we upgraded to exchange 2010 (or 14 as I've heard it called).  I lost the connection on my phone.  I tried changing the inheritable permisions above and it has not solved it.  I'm pretty sure all the log in info I'm using is correct.  It acts like it's communicating with the server because it says
    Unable to sign in
    Could not sign into account
    THe mail server responded: bad login/password
    I've changed several things and when I change certain things it says it cannot validate incoming mail server so I feel like I'm close but can't figure it out.  Any help would be appreciated.  Thank you.

  • 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 .

  • 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"

  • Getting FIOS Development Team to provide updates on the Idea Exchange

    What do we need to do to get the FIOS App Development team to provide updates to the Idea Exchange... We have been trying to get an update on the status of a Windows 8 or Windows Phone 8 App, and no one ever seems to want to respond.  It was posted and "acknowledged" back in 2012, with no Verizon update since.  Every time someone tries to repost the question, it quickly get's move to the old thread and then ignored by Verizon with no other response...

    What do we need to do to get the FIOS App Development team to provide updates to the Idea Exchange... We have been trying to get an update on the status of a Windows 8 or Windows Phone 8 App, and no one ever seems to want to respond.  It was posted and "acknowledged" back in 2012, with no Verizon update since.  Every time someone tries to repost the question, it quickly get's move to the old thread and then ignored by Verizon with no other response...

  • 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!

  • Finding similar ideas on the Idea exchange

    Ack, I had an idea and went to the idea exchange forum. Was wondering if this idea was already there, not wanting to pollute the forum. A "broken vi" search returned 55 hits. I cannot justify the time reviewing these before adding an idea. I'd like to be able to quickly submit an idea without the stress!

    Add a few more keywords to the search.
    Alternatively, just post the idea and somebody will very quickly point out if it is a duplicate.
    LabVIEW Champion . Do more with less code and in less time .

Maybe you are looking for