glennPattonWork wrote:

Any relation to Grace Hopper

No. The spelling is different.

Jason

I can't stand rewriting the same code twice. It's bad enough when it goes against the DRY grain in day-to-day coding, but when it's because you lost the code and have to rewrite it.. it's the worst feeling of wastefulness, so I try to avoid it (saving often, committing often, etc.)

Jason

This is basically what I do, doesn't everybody?

Jason

This annoys me too. I tell myself it's got to be driven by some misguided regulatory call, and not an actual belief that it makes your accounts more secure, or that it is overall worth it when you factor in the IT support costs, etc. It's part of my bullshit filter, true or not.

Jason

Chris Maunder wrote: cheers, Chris Maunder (CodeProject Admin) FOUND ONE! This isn't your normal sig. - Jason Do you have a Pulse? SonorkID: 100.611 [kritz] and if my os was any more up to date it would be made in the future

I've done it a different way (but thanks to all who answered). When I call the Init function in the .DLL I pass the handle of the window of my prog. Then the key function just sends a message to the main program that a key was just pressed. I use ::PostMessage(), and if I lose a key every now and then, it won't be missed among the million-or-so other keys a month I type. I can't wait to actually get this project going because I want to start letting the world know about it! :suss: -Jason nirgle.bitdevil.com

I get to be at work at 7:00am on January 1st! But hey, let's look on the bright side... mmmm... d'oh. -Jason nirgle.bitdevil.com

Heh! I have a relative that does this. Got to go to the bathroom? Going to be in there a while? Got half a plate of spaghetti to go? No prob! Let's multitask.. :suss: -Jason nirgle.bitdevil.com

Wait a second. Would it make more sense to have the .DLL increment a variable local to IT every time a key is pressed and the hook is called, and then export a function to return (and then reset) this value, so the main program can just call this func when it wants to, rather than the .DLL telling the program when it feels like it? -Jason nirgle.bitdevil.com

Hello. After a couple days of fitful studying of DLLs I still have one question that I can't seem to find hte answer for: I know the functions in a .DLL can do pretty much whatever they want, but how do I let the main program (that linked to the .DLL) know that something has happened in the .DLL. Specifically I want the keytrapping hook to let the keycounting program know "a key was just pressed". Is PostMessage the answer? -Jason nirgle.bitdevil.com

Very very odd that I suddenly read this. I finally sat down today to start development on my next project. (Think uptimes.org but with number of keys typed instead of current uptime). So I sit down and try to write a small .DLL that will have keytrap routines in it. Oh my god!! What a blatant display of proof to myself that I know absolutely nothing about Windows programming :) I was pulling my hair out all day and I eventually just gave up for the day. Will give it another go tomorrow after work :) :suss: -Jason nirgle.bitdevil.com

Flew over it once while flying from my hometown in Canada to its east coast in a Boeing jumbo jet in MS Flight Sim 2000. Everyhting is lovely from 30,000 feet :) :suss: -Jason nirgle.bitdevil.com

Bah! Mouse users. People who press WindowsKey + R to get the Run... dialog never have this problem :) (Or Ctrl-Esc, R for those without a Win keyboard) :suss: -Jason nirgle.bitdevil.com

Probably: - mIRC - VC ++ (even when not hacking, I love the html "syntax" coloring!) - MSDOS Prompt - IE 5 - WinZip - PSP 5 :suss: -Jason nirgle.bitdevil.com

Chris 17" Maunder :suss: -Jason nirgle.bitdevil.com

We have the exact same problem... my approach is simple and practical: I have 1 Notepad .txt file on my desktop where I won't lose it, and an icon shortcutting to it in my quicklaunch bar (because I never see my poor desktop, always buried by windows.) :suss: -Jason nirgle.bitdevil.com

I personally don't have any advice for you, but I know a book that might: http://www.wrox.com/Books/Book_Details.asp?ISBN=1861004761 I bought this to learn more about DB development and while I thought it was overly technical for someone with no DB devel experience like myself, the first third of the book is a fantastic and detailed discussion about the process of contracts with clients, how to work with them after you've agreed on a contract, etc. :suss: -Jason

But as we've both said now: tastes differ So at the end of the day, you'll have to try both and decide for yourself :) :suss: -Jason

Well put. I would counter that the keys that do things become automatic after a short time of (sustained) playing, so that once they're memorized enough, you can go right from thinking about what to do to actually having it done, without thinking conciously about how. But yeah, tastes differ. :suss: -Jason

I disagree! I think the $60 Canadian I paid for it was more than worth it. It's an entirely immersive experience, with more attention to realism than any other FPS I've played. The "slowness" of this game may make you feel that you're fighting the game, but that's the realism factor taking its toll. For instance, when you press Z to either hit the ground or get up off of it, your character actually goes through the movements, rather than just suddenly being in a state of laying prone, or suddenly being standing up again. Multiplayer is outstanding... but that's more me liking a concept rather than its implementation. :suss: -Jason