Hello,
Thank you for your response.
If the manufacturers of a camera has a driver, but proprietary API, means the functions content within DLL, and not known to us, how they actually do the function calls in the API (means the long pages codes for the USB comm and establish its enum...etc...)
Also, the manufacturer state the deriver can be used with third party software.
Is that means, we can use "LIBUSB" and microsoft samples to build an app, and add to it, canvas C# to place graphs and plot the image points?
One unique question: does the driver when accessed by "libusb" functions, can we "assume", that the manufacturers API, doing the same, and thus their function calls to do setup and commands, open and acquire and stop, will be on the same level of "Variable" contents, as they should be distinct and unique thus, not being changed, their types and byte size, etc.. will be the same ?
Unrelated question as why I find QT mentions and used in many application, instead of visual studio? the reason, some visual studion application state they using QT for graphic (I know they GUI and has graphic module separately), Is this because the window sdk multimedia not easy to use this this preferred in camera application, even some call their application Qxxxx?
Thank you for your help, appreciated.