|
Or maybe it's simply the Hamsters' Union.
|
|
|
|
|
Working on it
All fixed and should be available after next upload (in a couple of hours).
Sorry for inconvinience 
Sincerely,
Elina
Life is great!!!
Enjoy every moment of it! 
modified on Wednesday, February 25, 2009 10:48 AM
|
|
|
|
|
|
|
and I didnt know where else to post this.
I had a question posted in the C# forums that was likely too general to get a useable answer so I decided to delete it. There was a response to the thread but it was not particularly useful/relevant. I deleted my starting thread and a follow up reply of my own, then went to "vote to remove" the response from another user only to see that a message came up saying it was "reported as abuse". This was not intended and don't know how to fix or whom to message to state as much.
Sorry for any inconvienience this may have caused.
---------------------------------------------
Help... I'm embedded and I can't get out!
If they don't get the basic research and learning skills down then they'll end up having a very hard life (Either that or they'll become managers) - Micheal P Butler
|
|
|
|
|
|
Added. Will refresh in a few minutes.
|
|
|
|
|
|
I've made a note.
Thanks for taking the time to coach the author, Hans.
|
|
|
|
|
Can we ban user "MurderDolls" please? Annoying user that posts porn links all over the place.
See his spammy messages here[^].
Cheers
[d3m0n]
Email (replace "***" with "key")
|
|
|
|
|
Would it be possible to have the link View Member's Blog (on the member's page) optionally point to an external blog (like Blogger)?
|
|
|
|
|
Thta might be okay, except for the nefarious individual that wants to post a rogue URL meant to spread viruses, malware, and other crap.
"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." - Jason Jystad, 10/26/2001
|
|
|
|
|
Restricting to gold+ would fix that.
|
|
|
|
|
Not unless the requirements for attaining gold status were beefed up...
Besides, anyone can turn evil at any time, regardless of status.
"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." - Jason Jystad, 10/26/2001
|
|
|
|
|
The majority of the articles in the "Latest Articles" list at the bottom of the page appear to have nothing to do with the competition, specifically point 1:
"Qualifying articles must focus on Microsoft-specific technologies. The article and accompanying app must demonstrate "hybrid smart client" architecture: the app itself should run as a Windows client, preferably taking advantage of some technology like WPF. The app/client should consume some kind of web-based data feed."
Seems odd to me that only one of the articles, prima facie, seems to have anything to do with the competition - is this list supposed to be a list of entries, or is it a more general list of new articles?
print "http://www.codeproject.com".toURL().text
Ain't that Groovy?
|
|
|
|
|
Hi,
(Chrome V1.0.154.48)
I have noticed that if you hit the code block formatting tag to insert a 'pre/pre' the caret is not always placed in the centre of the 2 tags, but appears in inside one of the tags. This usually occurs if the caret position is right at the start of a line before pressing the code block label. If it is further in, it doesn't occur.
Also, sometimes the code block tags will jump down a couple of lines, on other occasions they immediately follow the text if your caret was at the end of some text.
The inline code also places the caret position within the first tag if it is the first thing on the line.
Cheers,
dave
|
|
|
|
|
Solution: Don't use Chrome.
"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." - Jason Jystad, 10/26/2001
|
|
|
|
|
As far as I can tell it's got to do with Chrome not updating information on the current cursor position after we insert text.
If you insert a CODE block, then click the code block insert button again, the problem show. If you click anywhere in between inserts the problem won't happen.
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
I liked the fact that when I was responding to a post, the original post I was responding to was in a blue square. It helped the eye be able to delineate the page a bit better. Now that it is all white I think it is a bit visually confusing.
|
|
|
|
|
That happened briefly to me yesterday during a site update but went back to normal afterwards. Have you tried forcing a refresh of you cache with CTRL-F5?
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots.
-- Robert Royall
|
|
|
|
|
Yeah, I just noticed that the blue area is back... must have been some kind of CSS thing that worked itself out.
|
|
|
|
|
So, in an attempt to beat this horse to death yet again, an idea came to me about how we could potentially make article submission just a bit better. At very least stop the offenders from being able to say they did not know what makes a good article, etc...
We have a few articles that details how to write a good article around here. We also have a ton of great input from the other writers that take their time top post high quality stuff. The problem is this:
1) It is scattered all over. Yes, I know, you can look for it, but if you don't know its there them...
2) there is nothing that makes a submitter responsible for viewing it before they have the right to submit an article. A lack of enforcement simply breeds ignorance.
So, I propose this. All new accounts, before they are able to submit an article, must go through a short 'class' that shows them what a real article is. This does not have to be something really complicated, but it should be substantial enough to maybe weed out the lamers that are trying to post questions and code snippets as articles. Maybe do a short video in Silverlight that they watch, or at very least a decent writeup on how to write an article, how the submission process works, etc...
...Then, test them on it. Make them go through a simple 10-20 question multiple choice test. Then, if they still create junk have the ability to reset their validation and make them go through it again the next time they try to do submit another article.
Yes, this may discourage people from writing articles a bit, but I think the people that see the real value in the good work will still do it, and the ones that don't, well we can just let them pass by I think.
Thoughts?
|
|
|
|
|
I do like the concept but testing adds a level of pain and suffering that is hard to automate, easy to bypass. I'm just not sure how it should be done.
Maybe a better idea is to force the author to view the article after posting with a big "Does this even remotely look good??" popup appearing?
|
|
|
|
|
To be honest, I am not sure if having a person review their own work is great simply because they wrote it and if they think it was good to start with it is going to turn into just another click for them. It may help catch the ones that are clearly mistakes using the tools but...
Would it really be difficult to come up with a 20 question multiple-choice test that you need to get an 80 or higher on before you can submit an article? Seems to me its just an attribute in the user profile that has their score and that the article submission process checks before allowing them in. This can be cleared back to 0 by the system if they get a poor rating in their submitted articles I think.
Just trying to come up with a way that is a small pain point for those that do a good job yet enough of a pain to make those that don't do a good job think twice...
Maybe its a lost cause 
|
|
|
|
|
Chris Maunder wrote: "Does this even remotely look good??" popup
Some great authors will thank you for that. 
IMO articles should go through an automated filter first. Just check a dozen things, yielding good and bad points (is there sufficient text? is there a download? are there some hyperlinks? is there some boilerplate text? is formatting disallowing automatic width adjustment?).
Now if the good points outweigh the bad points, list the bad points as suggestions and let the article through, no more "needing approval".
If the bad points outweigh the good points, reject the "article" and list the bad points as the reason for that.
And when in doubt (good and bad points almost balancing out), list the bad points as suggestions and let the author choose between "show to gold members for possible approval" or "I will retry soon".
Every "list the bad points" could mean: add a message listing the bad points, so if the article still needs approval, the goldies don't have to repeat what is already in there.
BTW At the moment I am no longer reading the "articles needing approval", main reason is messages we add disappear almost immediately for unknown reasons (new version posted? article approved?). It is just a waste of time. I'm now in favor of a user setting hiding them from the home page.
Luc Pattyn [Forum Guidelines] [My Articles]
- before you ask a question here, search CodeProject, then Google
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get
- use the code block button (PRE tags) to preserve formatting when showing multi-line code snippets
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
