Andreas Schulz wrote: > On Monday 14 July 2008, Stephen Warren wrote: >> 1) How was MAX_IR_SIGNAL_LENGTH chosen? Do we have any information on >> whether this correlates well with the official Logitech software? > > I didn't change that from the original version - looks like > 'ten times more than we will ever need, just to make sure it's enough'. > The longest code I have seen so far is 2*32 bits from my Pioneer DVD > player, which would need roughly 400 durations to record 3 repeats. > I have actually never tried what happens if you send a sequence of
Yeah, thinking about it, 500 pulses is probably just fine. >> 4) Can this function have progress callback added; either: >>... > > A typical reasonable duration for a IR signal recording is approx. > half a second or less, so I don't think that a progress indication > will be very helpful - besides the timeout indicator for start of the > recording that I added in congruity. Well, as you say, congruity certainly needs to display some kind of feedback to the user to indicate how long they have to start pressing the key on the original remote. congruity shouldn't know anything about how long this is; the actual timeout is implemented by libconcord itself, so it'd be best if progress was indicated directly from there, rather than congruity making assumptions about how libconcord works. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
