jporcher

@lassoan Thank you for your comments, I updated the code and hopefully the pull request (I'm not a Git expert). Please let me know if it looks OK now!

@lassoan Let me know if there's any action expected from me to have this pull requested be merged to your master.

@lassoan Sorry, but I'm not using the original CMakeLists.txt, I've written my own. In mine, I simply changed: `QT5_WRAP_CPP` to `QT_WRAP_CPP` `QT5_WRAP_UI` to `QT_WRAP_UI` `QT5_ADD_RESOURCES` to `QT_ADD_RESOURCES` Also had to...

As I mentioned, I did not use your CMakeLIsts.txt to build the library, so all the "changes" I did are commited. I have no more contribution available... I gave a...

@jamesobutler That would be difficult as this CMakeLists.txt has dependencies on other files of my project, but I can paste you some part of it: ``` set (LIBNAME qtcommontk) #...

@DavidEGrayson I believe I'm looking for the same feature, I'd like to access the product string: Under Windows, this is DEVPKEY_Device_BusReportedDeviceDesc Under Linux, this is "iProduct" reported by lsusb, "product"...

Sure, this can work. However, it would force to enumerate devices again as the API needs handles (OS IS as string won't help).

Actually, not sure it will work. get_os_id returns me "USB\\VID_0403&PID_6001\\AR0JFBPE" while SetupDiGetDeviceRegistryProperty with SPDRP_HARDWAREID returns "FTDIBUS\\COMPORT&VID_0403&PID_6001". So it's hard to safely determine if that's the same device or not (while...

Hi again, get_os_id() is "USB\\VID_0403&PID_6001\\AR0JFBPE" SetupDiGetDeviceInstanceId gives "FTDIBUS\\VID_0403+PID_6001+AR0JFBPEA\\0000" GetTextProperty/SPDRP_HARDWAREID gives "FTDIBUS\\COMPORT&VID_0403&PID_6001" So none fits. But this is maybe due to issue #10, looks like libusbp is pointing to "USB serial...

Just tested with a non FTDI device, using SetupDiGetDeviceInstanceId works fine to identify the device while enumerating using SetupAPI.