Re: [Libusb-devel] libwdi - installation of unplugged devices

[Xiaofan C. <xia...@gm...>]

On Mon, Apr 5, 2010 at 5:46 AM, Michael Plante <mic...@gm...> wrote:
>>> It really doesn't. As I explained, if you have a new USB device that
>>> needs a WinUSB driver, just run the app, and plug the device (before or
>>> after doesn't matter since the GUI app has hotplug), optionally confirm
>>> the name of the device and press Install.
>
> Hrm, maybe.  The screenshot seemed to imply quite the opposite, and I didn't
> see this vision/explanation or a mention of hotplug anywhere, so I think
> what I said was plenty reasonable at the time.

Hotplug support is in the GUI program. It knows the device plug-in
and unplug event. It is a useful feature that the GUI can inform the
user about the event.

>
> I would suggest that the GUI, in basic mode, take a VID/PID (or maybe a
> serial number) as a command line argument, since the developer already knows
> what that will be.  Maybe you already planned this?

Yes that would be good. Maybe the console program already did that
but I have not tested the console program for a few days.

>>> just trying to make the app look like something that
>>> "feels right" for the version of Windows they are using, as if it had
>>> come with the OS itself.
>
> To the extent that it's not a pain.

Agreed. It seems to me the one used in libusb-win32 infwizard.exe
is fine and has the right feel across XP/Vista/7 (should also be
right under Win2k but I never really used Win2k).


-- 
Xiaofan http://mcuee.blogspot.com