On 22-Nov-05, at 1:39 PM, Atte André Jensen wrote:
Graham Percival wrote:
I don't think this is the best solution,
I'm also interrested in the best solution. Could you give a few pointers?
No. :) I mean that literally -- I don't think I _can_ give you a best solution; it's not that I'm not willing to do so. It comes down to exactly what you're trying to do (and I don't know that), how you like to structure programs, etc. You could probably do this with classes -- make a HandleKeyboard class, then instantiate one of those for each keyboard. I think the best way to find the best solution is to go ahead and get it working, using whatever method(s) you can. Use that to learn about chuck, figure out exactly what you want to do, etc. Once that's all working, ignore your current program(s) and start again from scratch. Spend a week just thinking about the general design before programming anything. Of course, I've only taken one course on software engineering in my life, and that was in 1998. Nor have I done any programming since then, up until a few months ago. So I don't claim to be an expert. :) But that's how I would go about this. IMHO, the biggest problem is in deciding exactly what you want. Once you've done that, the actual design and programming is pretty easy. Good luck, - Graham