On 02/16/2014 10:26 AM, Scott Talbert wrote: > Yeah, I guess it seems OK. The things that are timing related are kind of > worrisome, but not sure what to do about them.
I could wrap the hid_exit() in an #ifndef __APPLE or whatever the define is, I guess. > Have you tested without hid_exit() on Linux? On Windows, it doesn't look > hid_exit() actually does anything. On Linux, it calls libusb_exit() - I'm > not sure what the consequences of not calling that would be. We probably > ought to be calling hid_exit() when concordance exits, though. Which > probably would mean adding a function to libconcord so that concordance > can call it when it is about to exit. I have tried it with and without on Linux and it doesn't make a difference. That said, I imagine when the process exits all your libusb handles get cleaned up anyway, and the refcounts in the kernel go back down. -- 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
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
