Dave, I have also noticed that I don't venture into the forums as much because of the new collapsed navigation menu. Your suggestion might solve that, but I would rather be able to see the whole menu.
I actually just came across this CP page[^]. Forget about the page content and look at the navigation bar. It really is very long and I can see why they decided not to display all of it, but I think I would like to have the option - perhaps in the bar where you set up the other forum options (Profile popups, Spacing, etc.).
Recently ,for my question somebody posted solution.I thought solution is good but not i asked for , hence I gave 3 out of 5 (single vote). Now he is complaining its down vote. Is it correct?Its down vote.
A 3 is neutral in the fact that it doesn't give negative or positive reputation points, but if a post has already got one vote of 5 and you give it a 3 then you are bringing the average down to 4, so effectively downgrading the 5. Similarly, if a post has a vote of 1 and you give it a 3 you are upping the average.
I think this is perfectly fine. In this case it is an answer in QA and if the OP felt it did not resolve the problem, the average should go down. In any case it should not hurt the member posting the answer. I would not object if I answered a question and received a 3-vote.
Had it been an article, you could argue that it hurts the author to have the average rating lowered even if there is no change in points. I do wish Code Project would change the 3-vote on articles so you don't have to leave a comment. There are people who take offense to getting 3-vote as this thread shows.
Apparently this post[^] has been flagged as spam (at least) 36 times, but it's still there. Aren't they supposed to be removed after a certain number of reports? (The account was closed though, so it looks like it's working there.)
OK, gather round kids and I'll tell you a story...
Our reputation system grew quickly from a simple system that awarded points for posting articles to a system that was very fine grained. The initial code to award points was baked into the stored procedures that created articles, but as it grew we found we were mixing two patters: one which baked calls to the rep system into the sprocs, and one which used our modular code system that listened to "events" that occurred and would react appropriately.
When we moved our reputation system from a site-centric to network-centric system we, by necessity, had to pull out all the code in the sprocs and move them into message handlers (ie do it properly). We have 77 rep events and dozens of event handlers and we got a few of them cross-wired. However, since I had turned off ratings in the forums, this had masked the issue, because the rating and reporting systems were connected (again, another TODO: untangle them).
It was a straight out bug on our part, and it's the same bug I'm fixing, Friday night, bottle of red, to ensure points are awarded when you edit a Quick Answer question or answer.