|
Baby steps first. Let's work on a "acceptable answer" (lower limit) then we can add a "Experts recommend" limit (upper). But yes, I do like that idea.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Thiru Thirunavukarasu wrote: had at least 2 votes with a rating >= 4.
I don't see much of 2 votes either! Which again would look like nothing has changed... In this case, system depends on viewer voting which too doesn't happen much in a Q&A forum!
Thus, i don't think this too would help much...
Alternative: Limit enquirer's on asking question until they close the last one... (lets say there can be a pool of maximum 3 open question of an enquirer at one time)... now cases available that needs discussion:
1. 3 open questions, none of them replied yet
2. 3 open questions, 1 or 2 replied but not appropriate answer
If OP wants to post new question, they need to close any one of them. Apart from 'Answer Accepted', there should be an option of 'No Answer/Answer not appropriate' or so (wordings can be decided later.)
This would give OP an option to close a question even if they don't get a proper reply.
Further, in a given period of time.. lets 2-3 days... if a question can be answered then generally it is answered... it rarely happens that question is answered after a week or so. Thus, its an auto reply to OP that no one currently can reply them back on the issue!
|
|
|
|
|
I think it's still a big step up. I'm sure there will still be a number of questions without an answer with at least 2 votes but that number will be much lower than it has been till now.
|
|
|
|
|
yes a step forward but i doubt if it is big... havent analysed much... but on a rough scale i found mostly one 5 vote... 2 or more is still rare...
|
|
|
|
|
Sandeep Mewara wrote: Limit enquirer's on asking question until they close the last one...
That's not acceptable. You could ask three questions to which nobody has provided an acceptable answer. At that point, you'd have to delete one to ask another. What a pain in the ass...
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
I don't see how someone else can deduce that an answer is viable or acceptable to someone else's question when they can't possibly know the basis for the question or the context in which it was asked.
If the OP doesn't want to mark any of the answers as "accepted", so what? I am not in favor of the new scheme. If it's not already done, award the OP 2 (or even 3) points if he accepts an answer, and let it go at that.
While I'm on the topic, why don't we get a rep point for leaving a comment?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
The "so what" is that those looking to provide answers to questions in need of answers will not have any way of easily filtering out those questions that have no lovin'
We're trying to reduce the time someone needs to spend to find things they may be able to help with.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I think it should be left up to the OP to mark it as accepted.
How about this for an alternative to letting other people mark an answer as accepted:
Have a "Worked For Me" button that anybody can click. This would start a comment so they can optionally leave a remark at the same time. When marked as "Worked For Me", the answer would have a blue check mark indicating that someone other than the original poster found the answer of value. The question itself would have a blue rectangle (in the list of questions) indicating that one of the answers "worked for me" for at least one user that was NOT the OP.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
We do have a task to implement reputation for comments.
|
|
|
|
|
I'm for it. On the flip side, I've seen authors mark an answer as accepted and them leave a comment saying that they couldn't get that answer to work.
Most people have no clue how to deal with this correctly or are just too self-concerned that they don't care to let anyone else know they had their question answered.
|
|
|
|
|
|
Hi,
Found some weird behaviour in the forums at the bottom of articles. Using Chrome 4.1.249:
When you click to expand an item in the forum, the browser jumps up the page a short way. I've had it happen in this article (Validation in Windows Presentation Foundation[^]) and repeated it in others.
Only minor, but rather irritating 
|
|
|
|
|
Also happens in Chrome 5.0.375.55
It's time for a new signature.
|
|
|
|
|
Are you still seeing this happen? I can't replicate it in Chrome 8.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I'm also using Chrome 8 and can't replicate it either.
|
|
|
|
|
1.
inside forums, I'm currently failing to get a trailing space highlighted.
It seems a SPAN tag eats the consecutive space completely.
case in point[^]
[ADDED] #1 is solved, consecutive spaces get compacted ignoring tags. See rest of this thread.[/ADDED]
2.
It somewhat resembles the very annoying bug where any closing tag eats the consecutive newline; reported a couple of times, never got fixed.
3.
A related issue is: when selecting some text, in order to apply a style change (e.g. underline), it automatically includes a trailing space in the selection, if present. Which is probably harmless for some (bold, italic), but no good for others (underline, strike-through, big).
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
modified on Thursday, May 27, 2010 10:49 PM
|
|
|
|
|
Which browser? Works fine for me in IE7/8, Firefox and chrome.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Chris Maunder wrote: Works fine for me in IE7/8, Firefox and chrome.
Really?
All points: message created, previewed and viewed using FF3.0.19
First point also checked with IE7 (create, preview and view): space gets eaten also.
I was trying to get {SPACE}and{SPACE} with the spaces clearly visible, but was not getting that at all. It also fails when leading space gets replaced by a
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
modified on Thursday, May 27, 2010 10:21 AM
|
|
|
|
|
My apologies. You said "leading" I read that as "trailing".
No, it doesn't work for me either. However, I'm unsure if there is anything we can do about it. We're rendering in standards mode and the CSS is clear. It seems a browser quirk.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Chris Maunder wrote: It seems a browser quirk.
I'm a bit surprised then, as multiple, independent, browsers make the same mistake.
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
|
|
|
|
|
I may have spoken too soon. I've been doing some tests and I can get leading spaces highlighted easily outside of our stylesheet.
It's our problem, I'll fix it.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
OK, this is weird.
First <span class="highlight"> second </span> third
First<span class="highlight"> second </span> third
First <span class="highlight"> second </span>third
Gives:
First second third
First second third
First second third
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Chris Maunder wrote: OK, this is weird.
Well, maybe it isn't.
This code:
1.First <span style="background-color: #FFFF00"> second </span> third<br />
2.First<span style="background-color: #FFFF00"> second </span> third<br />
3.First <span style="background-color: #FFFF00"> second </span>third<br />
4.First <span style="background-color: #FFFF00"> second </span> third<br />
5.First<span class="highlight"> second </span> third
gives:
1.First second third
2.First second third
3.First second third
4.First second third
5.First second third
in a simple, non-CP, web page using FF3.0 (except for line 5, needs CP styles)
and I explain it like this:
- lines 2 and 4 are no surprise;
- lines 1 and 3, ignoring tags, have consecutive spaces; all but the first get eaten, as it is outside PRE tags;
- line 5: seems like you fixed something I did it right this time (no space before opening SPAN tag!).
The space reduction should (my opinion, maybe W3C thinks differently) take into account the spaces having different attributes.
Anyway, as it is now, I can get what I want as line 5 demonstrates.
Thanks for making me see the light.
PS: Of course there still are issues 2 and 3 in my OP.
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
modified on Thursday, May 27, 2010 10:45 PM
|
|
|
|
|
I say hello to you.
In the above sentence, I see "hello " highlighted while I'm expecting " hello " to be highlighted (i.e., the leading space isn't highlighted, which seems incorrect to me). Looks like Code Project doesn't do anything special with the rendered HTML though, so I'd call this a browser bug or quirk.
I'm using IE8 on XP Pro.
Luc Pattyn wrote: It somewhat resembles the very annoying bug where any closing tag eats the consecutive newline; reported a couple of times, never got fixed.
Yeah, that bug is annoying. I sometimes have to insert BR tags to workaround it. By the way, this is the HTML I used for the sentence at the top of this post:
I say <span class="highlight"> hello </span> to you.
|
|
|
|
|
Good evening to you too.
aspdotnetdev wrote: I sometimes have to insert BR tags to workaround it
huh? I simply put a space between > and NewLine and that seems to fix it every time; and each time I forget, I have to correct it.
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
