🚀 go-pugleaf

"Kris" <x.y@xyz.xx> wrote in message
news:3qbft19f0602l0f1m44t2uhiuio593trh1@4ax.com...

> Such operations are accompanied by following message :
> WM_DEVICECHANGE : DBT_DEVNODES_CHANGED

That only works on Win2000 and later.

I would suggest using DBT_DEVICEARRIVAL and DBT_DEVICEREMOVECOMPLETE
instead.  They tell you the specific device that was added/removed, and they
are available on all OS versions.

> Any ideas on how to accomplish this ?

According to the documentation for DBT_DEVNODES_CHANGED:

    "There is no additional information about which device has been added to
or removed from the system. Applications that require more information
should register for device notification."

Look at the RegisterDeviceNotification() function.

> Should I just wait a little bit longer, e.g. treat all
DBT_DEVNODES_CHANGED
> in a 2 second time-span as one DBT_DEVNODES_CHANGED message
> that will then trigger a new device scan ?

No.

> I was also looking at using DBT_DEVICEARRIVAL and
> DBT_DEVICEREMOVECOMPLETE. Unfortunately,
> these events are also sent when I remove or insert a CD in the drive.

So?  You can filter those out before deciding to scan your devices.  Or,
don't even scan at all.  Use the details inside those notifications to
add/remove just those specific items to/from your list instead of refreshing
the entire list as a whole, since notifications are sent on a per-device
basis to begin with.

> Connect device :
> DBT_DEVNODES_CHANGED
> DBT_DEVNODES_CHANGED
> DBT_DEVICEREMOVECOMPLETE
>
> Remove device :
> DBT_DEVNODES_CHANGED
> DBT_DEVNODES_CHANGED
> DBT_DEVNODES_CHANGED
> DBT_DEVICEARRIVAL
> DBT_DEVNODES_CHANGED

Are you sure you have that right?  You get a removal notification when you
connect a device, and an arrival notification when you remove it?


Gambit