|I can see the other members are really trying to help you and I can see that you're attempting to make changes, but ultimately your changes are small and not enough.
If you please, let's try a different exercise here. For this article only, let's change the goal. The goal is not to get the article published. The goal, for now, is to get better at writing an article for CodeProject. Think of it that way.
Throw your existing article completely out. Start over from scratch. The first step that might be helpful is to make a rule for yourself. Write more words than code. Put it into a word counter if you have to. Write out what the code does, rather than show it.
Also, truly look at the following article by one of our top authors. Don't skim over it, don't skim over this message. Read every word. Think about it. Think about this author's approach in how it differs from your own. CodeProject readers are primarily looking for meaty, exhaustively explained solutions to their development problems, or articles that can teach them something to make their developing faster, more efficient, or expand their repertoire.
Here’s an article from one of our top authors:
HTML5 WebWorkers Experiment[^]
His primary goal is to demonstrate “Using HTML5 WebWorkers and a custom jQuery plug-in to create a Flickr image wall.” He treats the reader like a beginner. He defines jQuery, explains what WebWorkers are, then gets into why he wanted to create a jQuery plugin. Each progressive section of the article expands on his topic, thoroughly explains the code, explains the limitations he chose in his scope, discusses how each element to his plug-in works, provides numerous code examples, and most importantly, gives a source code download at the top for the reader should they need it.
Every time the community considers whether or not to approve an article, this is the style of article they have in mind. They love it, they want it, and they praise the authors enormously when they get it (and we want authors to feel like their hard work is appreciated).
If you can fundamentally change your thinking here, and you can fundamentally change your approach, we're happy to continue working with you. There's no short cut to getting an article published. Put in the time, make the effort. Take a week or longer.
If you come back with minimal changes, that's the end of the road. I don't think you're right for CodeProject. We won't consider any more of your future articles. And that's OK. Some people and institutions don't fit together. But we could. You just have to decide to put in the work.