On 03/20/2012 06:18 AM, Scott Talbert wrote: > Well, the only case I'm thinking of is: > a) insert remote > b) run "concordance -i" to check if remote is seen by concordance > c) in this case, concordance doesn't retry several times, it just fails > (if within the ~5 second window) > > The retry count only applies to resets, so if a remote is reset, > concordance will keep trying to connect to it.
Ah. I suspect most users will be using congruity and go through the site which will take longer than 5 seconds, but this is certainly something to consider. I'm wondering if we want to figure out that it's a usbnet remote by USB vid/pid and behave differently. We can short-circuit FindRemote, if we don't find a remote, we can print a message saying that we're waiting for 5 seconds for the remote to be configured on the network, etc... The only concern that I have is that they've come out with new HID remotes since then and worry there's not a nice way to say "this range is usbnet and this range is HID" kinda thing. -- Phil Dibowitz p...@ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
