not that it matters, but I don't program C because I don't have a need for it (C is only better than other languages for low-level - such as hardware - stuff) and I also don't program python because as you eluded to it is for noobs (hence why you use it). I personally program PHP/JS/HTML/CSS/SQL mainly (that's what I get paid to do sometimes at the moment) but I get paid to do Delphi programming (although not as much as I used to). Your code was actually the first piece of python that I've ever debugged... its just a pity you seem to be incapable of doing the same.
Easy - ALLOW for it during your checks in your filtering tests!
you're right that it is easy to filter inputs, but not on keypress. you will need another event to handle that. that's why i mentioned events such as lostfocus, but there are of course others (keypress is definitely one event that can be used for partial input validation, but not on its own).
if you have your so called "filter tests" (noobish terminology much) only in a keypress event, you will either allow invalid input (such as a lone "-" symbol) or you will prevent entering of valid inputs (such as "-5.4" for example).
you are about as noob as they come APK, but you are definitely the most arrogant self-rightious noob I have ever come across, which makes you look even more stupid on this very public and open forum.
Oh, so NOW 'CruTcHy' (lol) "flips the script" changing what he said, lol, "adding on to it"
i quoted from the original message dipshit. i didn't add anything.
getting pretty desperate aren't you?
On user inputs, you USE KEYPRESS EVENTS in entry fields to trap bad data users may input.
that's one way, but not necessarily the best because you may be trying to validate incomplete user input, so if a user startes by entering a minus symbol with the intention of entering a negative number, how can you validate that on keypress? the next key may be a number, which would make it valid, or they may move on leaving just an invalid minus symbol. using a keypress event handler is similar to a change event handler in that you can do something non-intrusive (like change the color of the text box label to red) as the user types until a valid input is achieved, but you shouldn't show any kind of intrusive error message until the user has actually finished entering their input (with an lostfocus or similar event).
anyway, i know you won't even read this let alone understand it.
you're also starting to get boring APK, so unless you can step up the intelligence of your conversation i'm probably going to move on
you either never read the code that you post, or you really are ignorant of the bug in it... you can't hide it because you keep posting the same code for all to see:)
i really don't care much about your code or your bug, but its fun stiring you up about it, and there is a bug in the posted code - the code you supposedly run is apparently not the same as what you post, but whatever... noob
the difference comes about when you have 3 x 40"+ eyefinity (or similar) setups. you definitely want a decent frame rate or you gunna have epileptic fits
parts fail regardless of whether you build yourself or buy oem... the difference is that oem shit is likely to fail sooner (as soon as the warranty runs out) and unless you're willing to pay a premium for after sales service, you'll get nothing but runarounds and idiots on the phone that you can't even understand when you need to get something fixed.
i buy parts from my local store owner, who i can talk to in person and he's a local too. he gets parts as part of a national network, so cost is very cheap for decent brands.
he's obviously never heard the age old (and oh so true) saying "happy wife, happy life"
i'm sure there are husbands that feel the need to "be the man" and "wear the pants", but they really are the idiots of the married world, and will often be the ones that end up a multiple divorcee.
Slashdot Mirror
Easy - ALLOW for it during your checks in your filtering tests!
you're right that it is easy to filter inputs, but not on keypress. you will need another event to handle that. that's why i mentioned events such as lostfocus, but there are of course others (keypress is definitely one event that can be used for partial input validation, but not on its own).
if you have your so called "filter tests" (noobish terminology much) only in a keypress event, you will either allow invalid input (such as a lone "-" symbol) or you will prevent entering of valid inputs (such as "-5.4" for example).
you are about as noob as they come APK, but you are definitely the most arrogant self-rightious noob I have ever come across, which makes you look even more stupid on this very public and open forum.
btw, have you found that bug yet?
the entire intertubes in the US is controlled by one entity... the MPAA
the rest of the world would probably do a whole lot better if the US was cut off
maybe different code ran (maybe you just typed the "output" manually), but the code that you post won't run with the indentation bug on the 5th line
Oh, so NOW 'CruTcHy' (lol) "flips the script" changing what he said, lol, "adding on to it"
i quoted from the original message dipshit. i didn't add anything.
getting pretty desperate aren't you?
On user inputs, you USE KEYPRESS EVENTS in entry fields to trap bad data users may input.
that's one way, but not necessarily the best because you may be trying to validate incomplete user input, so if a user startes by entering a minus symbol with the intention of entering a negative number, how can you validate that on keypress? the next key may be a number, which would make it valid, or they may move on leaving just an invalid minus symbol. using a keypress event handler is similar to a change event handler in that you can do something non-intrusive (like change the color of the text box label to red) as the user types until a valid input is achieved, but you shouldn't show any kind of intrusive error message until the user has actually finished entering their input (with an lostfocus or similar event).
anyway, i know you won't even read this let alone understand it.
you're also starting to get boring APK, so unless you can step up the intelligence of your conversation i'm probably going to move on
you CAN'T EVEN PROGRAM IN C
just because i don't doesn't mean i can't
and i get paid for programming php/html/js/css/sql, so why would i give a shit about c?
you either never read the code that you post, or you really are ignorant of the bug in it... you can't hide it because you keep posting the same code for all to see :)
jealous much :)
"output data" that you probably manually typed
i really don't care much about your code or your bug, but its fun stiring you up about it, and there is a bug in the posted code - the code you supposedly run is apparently not the same as what you post, but whatever... noob
the difference comes about when you have 3 x 40"+ eyefinity (or similar) setups. you definitely want a decent frame rate or you gunna have epileptic fits
sometimes graphics cards even have their own molex connector
graphics
hey i can't help it if i'm just that irresistable
poor APK... sucks to be him :)
... or i could go buy a new car for the same price :)
linux is even easier (well, debian anyways)
parts fail regardless of whether you build yourself or buy oem... the difference is that oem shit is likely to fail sooner (as soon as the warranty runs out) and unless you're willing to pay a premium for after sales service, you'll get nothing but runarounds and idiots on the phone that you can't even understand when you need to get something fixed.
i buy parts from my local store owner, who i can talk to in person and he's a local too. he gets parts as part of a national network, so cost is very cheap for decent brands.
based on personal experience, and since i don't use windows, its cheaper (unless you're an idiot and buy your parts from an oem)
he's obviously never heard the age old (and oh so true) saying "happy wife, happy life"
i'm sure there are husbands that feel the need to "be the man" and "wear the pants", but they really are the idiots of the married world, and will often be the ones that end up a multiple divorcee.
psu's are surprisingly expensive given that most modern decent systems need at least 700W
i find that oem boxes will come with the minimum required for installed hardware, leaving no room for upgrading
fortunately even if i spend $100 on a half decent psu i'll still finish up trumps compared to an equivalent spec'ed oem box
those who reckon oem is cheaper are merely the dupes trying to justify being ripped off
you obviously never built your own
...but then again i also install debian, not winblows
i build all my pcs and i won't buy unless i can make up at least a 50% saving compared to retail oem
lol that's a stretch... actually its more "cheapskate consumer" (i get more bang for my buck with AMD), but whatever
go find your bug, idiot
he hasn't. he's an ameteur noob, and a stupid one at that. at least i get paid to develop software.
His post's a compilation of verified facts on security mishaps in Linux.
no its not... try actually reading them and you will understand why
I took a look at his code and it ran 5 times perfectly in front of you.
i don't care what supposedly "ran"... at the end of the day the code that is actually posted has a bug