On Friday 15 December 2006 16:12, Melchior FRANZ wrote: > * leee -- Friday 15 December 2006 17:04: > > I've replaced most of the listeners, at least all the high-frequency ones > > that were being called every frame, with timers [...] > > It doesn't make much sense to attach listeners to properties that > change several times per frame. In that case a settimer(..., 0) is > better. But in most other cases listeners are more effective.
I needed to intercept all the stick inputs and listeners seemed like the best idea, in theory, because none of the stick input would be missed and in addition to this I also needed to constantly monitor stuff like attitude/orientation and velocities etc. Using a timer means that I'm only getting a periodic sample input. With a high enough rate it shouldn't be a problem and 0.1 seconds seems to work well enough. > > > It does seem to look like some sort of listener related problem. > > I'd really like to see the code. There was probably some other > problem. Do you remember Josh's listener problem? It was just > buggy code. The listener was fine. :-} > > m. It's all in the current cvs version - from the sounds of it Georg V has been able to duplicate the problem with the cvs version. Please do look over it if you have the time - it's quite possible I've done something dumb in there, apart from the duplicated filter I found. There's quite a lot of stuff there though and it interacts in some quite complicated ways - I'm still thinking about different organisational schemes. LeeE ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
