A vote down can only speculate on the outcome of the suggested idea. If one does not like the idea he simply does not vote for it. If the idea is implemented and one does not like it then don't use it - others who like it will do.
A vote up can only speculate on the outcome of the suggested idea.
If that is what you believe then voting is not the way to promote ideas.
Sometimes the functionality of how a command or attribute works performs well for the design flow of one user. Altering it could cause a workflow impediment.
So I can understand the vote down.
Agree! I have experience this with many Releases! where added functionality/options breaks a process/workflow that helps users!
I agree too. It would help SW to know whether people are actually opposed to certain changes or if most people just don't care one way or another. An idea where half the users would love the change and half the users would hate the change should have less chance of being implemented than an idea where half the users love the change and the other half don't care either way.
I disagree. Again: If you don't like an implemented idea simply don't use it - others will do.
But some of the ideas involve changing existing functionality. I could create an idea that says "Pressing escape key should quit SolidWorks without saving documents." That is a stupid idea that would mess up of lots of people, so they should be able to vote it down. If the idea is implemented they can't just "not use it", they would be forced to change their workflow to accommodate it.
Boyko Tchavdarov wrote: Again: If you don't like an implemented idea simply don't use it - others will do.
Boyko Tchavdarov wrote:
Again: If you don't like an implemented idea simply don't use it - others will do.
I disagree with this. There have been several "enhancements" in recent years that I intensely disliked, and couldn't turn off. I think they've all been fixed in later editions, but it wasn't something I could just not use if I didn't like it.
Example: In 2007 SW implemented a new scheme for how SW searches folders for files. This "improvement" cost many users countless hours of lost time. The end result of the change was that SW was more likely to find a missing file, but even more likely to pick a wrong version of a file.
The "note combining" feature, when they were moved a little too close to each other was one of the ones I had in mind. Hiding components with the Tab key is another.
Un-wanted drop-downs obscuring the box beneath them are another "enhancement" that can't be turned off. When entering the spacing for a linear pattern, I don't need the drop-down covering up the box for number of instances. I never use it, but I can't turn it off.
In 2012 they Re-Did the Equation Dialog completely. We had a lot of Master Models setup and had to work MONTHS to have them working properly again!
In 2011 they Added Multi Body SheetMetal. This was the Worst Idea ever and there are still issues originated by that "Enhancement"
This and other comments on the same is a different story that should be told. Solid Works should count on and improve the development work,
Nothing in SW is used only by one users.
Supposed 50.1% of all SW Users likes the idea and voted UP while the rest of the Users don't like it and voted DOWN. Then an idea which is liked by the majority of the SW Users will receive very few votes and won't be implemented. At the same time an idea which is liked and voted UP by only one 1% of all Users but none of the users vote against it will receive more votes and will be implemented. That is what votes DOWN can do.
The true problem here is that the 50.1% of "Voting users" is just 100 out of 2.5 million users! So I agree with you in the sense that simple Voting up and Down for Ideas is not the best way to implement functionality, Especially the one one that changes existing functionality
I guess it be smart to implement a SCORING System for users to vote on Ideas:
SW Employee 5 points (Per Vote)
Application Engineers (VAR) 5 Points
CSWE 4 points
CSWP 3 points
CSWA 2 points
Regular User 1 point (or based on their level number on the forums)
Something that shows the true value of good ideas and their feasibility!
im paraphrasing here but,niels bohr once said " there are great truths and there are simple truths. the opposite of a simple truth is false, the opposite of a great truth ,is still true"
I get your point. But the problem is that your change might garbage up the interface for everybody. For example, you might want three types of holes added to the hole wizard. But I might vote it down because I don't want to wade through a bunch of holes that are never used by normal people to get to holes that account for 99% of what normal people do.
Another example, you might say, I want a warning added so that, if I change a hole callout, it will warn me that it breaks the link. I'd vote that down, because if I ever find the guy that invented that warning, I'm seriously going to kill him.
Guys, really it's not something to worry about.
1/ I come across an idea
2/ I vote on it
3/ only to come to the realisation that I vote wrong and so I change my vote
Result is that the original 4 votes becomes 4 votes after I voted it down.
In other words the voting process itself has problems.
To sum up my opinion. Voting DOWN make sense ONLY if any idea is read by the same number of people that have a choice a vote UP, DOWN, or restrain from voting - similar as in any decision making group of people However, we cannot consider that those who did not cast their votes have read the idea - most of them have not and have no idea what it was about. If they do they probably will vote UP or DOWN. We never can guarantee that all Users have read all ideas that is why I believe voting only UP is fairer choice for the best ideas to get more points.
Retrieving data ...