I have built devices that has had to cope with dodgy hardware inputs like that. In theory they did the debounce (real debounce) so I called my function SuperDebounce :-)
Its not like we don't have heaps of other hacks to work around hardware issues in XCSoar, lots of software programming is like that. Scott On 03/04/2012, at 4:40 PM, Max Kellermann wrote: > On 2012/04/03 07:45, Matthew Turnbull <matth...@talk21.com> wrote: >> Seems that the debounce field has been removed from the config. Can you log >> a ticket in the bug tracker. > > If hardware buttons are handled twice, then debouncing is not the > solution, only an ugly kludge. > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Xcsoar-user mailing list > Xcsoar-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcsoar-user ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
