DirectInput best practice

Hi everyone,

Im working on a game and I want to add control. (Don't worry, everything is coded for how control will work with game object) I was thinking about a Thread based systeme to handle input from keyboard and mouse. Im just asking if some of you know the "best practice" to handle user input. I mean, do it's better to have one thread for keyboard and one for mouse, or one big brutal thread for all control ? Im of the advice that smaller function are better, but i want to have some opinion...
Thanks!

p.s. Sorry for my english, im not english

[576 byte] By [Hardone] at [2008-2-5]
# 1

Are you referring to putting these into separate functions or separate threads?

Separate functions are a matter of personal choice and won't affect much.

If your talking about separate threads, you don't need separate threads to read input and it won't help much but if want to do separate threads, it will require that any data shared between threads be synchronized and this is which is a fairly complex subject. Search for "multithreading" on MSDN or a search engine for more info about this.

JasonSa at 2007-9-9 > top of Msdn Tech,Game Technologies: DirectX, XNA, XACT, etc.,Game Technologies: General...