Ego-driven voting system and retaliatory voting/comments. No more.
-
I'm dafür!
I'm not. The 2nd world war was a really terrible war. A lot of good people died back then. My grandfather for instance, died in a German concentration camp... :sigh: .... he fell off a watch tower! :~ OK; that was really bad - that's why I posted it in the Lounge where people can't downvote it... ;P
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932 -
I'm not. The 2nd world war was a really terrible war. A lot of good people died back then. My grandfather for instance, died in a German concentration camp... :sigh: .... he fell off a watch tower! :~ OK; that was really bad - that's why I posted it in the Lounge where people can't downvote it... ;P
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932:laugh: :laugh:
cheers Marco Bertschi
Software Developer & Founder SMGT Web-Portal CP Profile | Twitter | Facebook | SMGT Web-Portal
FizzBuzz - Gary Wheeler
-
I'm not. The 2nd world war was a really terrible war. A lot of good people died back then. My grandfather for instance, died in a German concentration camp... :sigh: .... he fell off a watch tower! :~ OK; that was really bad - that's why I posted it in the Lounge where people can't downvote it... ;P
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932Johnny J. wrote:
OK; that was really bad - that's why I posted it in the Lounge where people can't downvote it...
Wanna bet?
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
Johnny J. wrote:
OK; that was really bad - that's why I posted it in the Lounge where people can't downvote it...
Wanna bet?
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easierDownvote - No Report abuse - Yes But you wouldn't do that to poor me, would you now? :confused:
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932 -
Downvote - No Report abuse - Yes But you wouldn't do that to poor me, would you now? :confused:
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932I wouldn't, but I'm not the only one who reads the messages.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
So this is the comment. Got a 1 vote for it. http://www.codeproject.com/Messages/4491610/PostQuitMessage.aspx[^] Sorry for bringing this (again) to attention, but I think the (down)voting system become far too retaliatory to do any good. About the comment: the article explain a hooking/subclassing system, which calls PostQuitMessage from a dll. PostQuitMessage will execute in the context of the "hooked" process and this will most likely have as a result ending of its message loop. So the unload/unhook/uninit/whatever will close the injected process (abruptly), which is unacceptable. So - is it a playground here or a hi5 forum? or is it a programming one? Because if anyone interested in process injection (and not only) fails to understand my previous comment, then I suppose is not only better *not* to comment or reply on what PostQuitMessage does in this context - but maybe is time to let Windows programming for those who can handle it. Think that many juniors can take this for granted and bomb their own implementation, customers gets crashed etc. Really, this is *not* a subject to trifle with without a gazillion of precautions. Or to vote down just for some unjustified ego reasons. I invite the person that voted 1 for this comment to step forward and explain why there is no value in my comment. This type of charade is happening long enough for me to stop ignoring such things and fight back for my ideas. Really, CP (or for that matter, *any* programming forum) it is supposed to consist of members contributing (keyword !) to a community of programmers. We're not on Facebook here to throw with Likes just because an article or a comment is of a friend. So - where do we want to go next? Facebook style, or coding?
Nuclear launch detected
Cristian Amari
So - where do we want to go next? Facebook style, or coding?
There are many reasons why people down vote. There is no rational in taking such things seriously. You put your opinion, for those are able to understand it will help. Like Facebook, CP also gives right to have people their own point of view. In that CP is Facebook style. However people with right attitude about learning programming and adding value will always be appreciated.
Happy Programming
-
So this is the comment. Got a 1 vote for it. http://www.codeproject.com/Messages/4491610/PostQuitMessage.aspx[^] Sorry for bringing this (again) to attention, but I think the (down)voting system become far too retaliatory to do any good. About the comment: the article explain a hooking/subclassing system, which calls PostQuitMessage from a dll. PostQuitMessage will execute in the context of the "hooked" process and this will most likely have as a result ending of its message loop. So the unload/unhook/uninit/whatever will close the injected process (abruptly), which is unacceptable. So - is it a playground here or a hi5 forum? or is it a programming one? Because if anyone interested in process injection (and not only) fails to understand my previous comment, then I suppose is not only better *not* to comment or reply on what PostQuitMessage does in this context - but maybe is time to let Windows programming for those who can handle it. Think that many juniors can take this for granted and bomb their own implementation, customers gets crashed etc. Really, this is *not* a subject to trifle with without a gazillion of precautions. Or to vote down just for some unjustified ego reasons. I invite the person that voted 1 for this comment to step forward and explain why there is no value in my comment. This type of charade is happening long enough for me to stop ignoring such things and fight back for my ideas. Really, CP (or for that matter, *any* programming forum) it is supposed to consist of members contributing (keyword !) to a community of programmers. We're not on Facebook here to throw with Likes just because an article or a comment is of a friend. So - where do we want to go next? Facebook style, or coding?
Nuclear launch detected
-
So this is the comment. Got a 1 vote for it. http://www.codeproject.com/Messages/4491610/PostQuitMessage.aspx[^] Sorry for bringing this (again) to attention, but I think the (down)voting system become far too retaliatory to do any good. About the comment: the article explain a hooking/subclassing system, which calls PostQuitMessage from a dll. PostQuitMessage will execute in the context of the "hooked" process and this will most likely have as a result ending of its message loop. So the unload/unhook/uninit/whatever will close the injected process (abruptly), which is unacceptable. So - is it a playground here or a hi5 forum? or is it a programming one? Because if anyone interested in process injection (and not only) fails to understand my previous comment, then I suppose is not only better *not* to comment or reply on what PostQuitMessage does in this context - but maybe is time to let Windows programming for those who can handle it. Think that many juniors can take this for granted and bomb their own implementation, customers gets crashed etc. Really, this is *not* a subject to trifle with without a gazillion of precautions. Or to vote down just for some unjustified ego reasons. I invite the person that voted 1 for this comment to step forward and explain why there is no value in my comment. This type of charade is happening long enough for me to stop ignoring such things and fight back for my ideas. Really, CP (or for that matter, *any* programming forum) it is supposed to consist of members contributing (keyword !) to a community of programmers. We're not on Facebook here to throw with Likes just because an article or a comment is of a friend. So - where do we want to go next? Facebook style, or coding?
Nuclear launch detected
PostQuitMessage would could close the injected process only if this was on the main message loop. Even then, you assume it isn't doing something else with the resulting WM_QUIT message. In this regard, you answer is technically incorrect, though your concern is correct and the use of PostQuitMessage is extremely bad and totally wrong in this situation.
-
PostQuitMessage would could close the injected process only if this was on the main message loop. Even then, you assume it isn't doing something else with the resulting WM_QUIT message. In this regard, you answer is technically incorrect, though your concern is correct and the use of PostQuitMessage is extremely bad and totally wrong in this situation.
Point taken. But from article the whole thing is done in main thread, and one cannot rely on what the injected exe does handling WM_QUIT or not (anyways this can is cancelable only with custom code). For sure I could have been expanded the answer, but I thought the idea was clear enough.
Nuclear launch detected
-
There was a time when posting this type of complaint here would guarantee you several more downvotes, and ones that actually affect your rating, too. That thread is over a month old, why do you care about getting a 1 today?
It's about the idea, not when or what. I am not complaining about the 1 - I got my share of well-deserved slaps in time. Simply put, this kind of thing makes me to edit bookmarks, and wonder myself when contributions becomes Likes. That's all. (And there was a time when this kind of thing didn't happened).
Nuclear launch detected
-
It's about the idea, not when or what. I am not complaining about the 1 - I got my share of well-deserved slaps in time. Simply put, this kind of thing makes me to edit bookmarks, and wonder myself when contributions becomes Likes. That's all. (And there was a time when this kind of thing didn't happened).
Nuclear launch detected
Cristian Amarie wrote:
And there was a time when this kind of thing didn't happened
What Utopia are you living in? This has happened on CP for as long as there's been voting on the articles.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
Getting a uni voter for a comment is a sign you are now, officially, a CPer.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
There was a time when posting this type of complaint here would guarantee you several more downvotes, and ones that actually affect your rating, too. That thread is over a month old, why do you care about getting a 1 today?
Well, at least the **** hit the fan. My comments on that thread are suddenly down voted :D. No other real contribution, no replies, just 1's. That's fine with me, only I think this proves my point. At work, if someone bombs/crash/dumps, the **** storm is immediate. Frankly, I think this is a good thing, we're arguing (and not pleasant) each other, but in the end the result is a better code. And I think that's the stuff to achieve.
Nuclear launch detected