incorrect
-
Tyn
- Gremlin
- Posts: 195
- Joined: Mon Jul 19, 2004 11:40 pm
- Location: England
- Contact:
Right, it's in the input somewhere. If you haven't got a line number, I guess someone could search for the line in the code, have you got a reason why this is wrong, or even better, a patch? Prehaps it's a textbook error and others will make a fool of me by showing it's obvious, but I have no idea what the problem is that needs fixing, so I'd hazard a guess that neither will the people who can actually commit the fixes to the CVS.
"A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
http://www.spacecolonization.net
2080: Space Colonization
Douglas Adams
http://www.spacecolonization.net
2080: Space Colonization
- sinbad
- OGRE Retired Team Member

- Posts: 19269
- Joined: Sun Oct 06, 2002 11:19 pm
- Location: Guernsey, Channel Islands
- x 67
- Contact:
I think 'correct' is open to interpretation. The existing implementation only feeds input to the active window, your method feeds input if the mouse simply passes over it. Neither is correct or incorrect, they're just different. Our input approach is a simple one based on a dedicated app; if you want more flexibility (e.g. tool creation) then you should be creating your own external window and managing input exactly the way you want using that.