Clarification on the Stopped state

[hanabanana]

I read in the paragraph under the image that "The watcher will transition to the Stopped state once all events that are already in the process of being raised have completed.". But in the image, the line from Stopping to Stopped says "All events that were in progress have been raised".

So when device watcher comes to Stopped state, does that mean all events have been raised(event callback might still be running) or all event callbacks have completed?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ed376899-7f17-12f3-b364-97e218a948bd
• Version Independent ID: 825ec2a5-c98a-78de-9001-819859593382
• Content: DeviceWatcher.Stop Method (Windows.Devices.Enumeration) - Windows UWP applications
• Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.devices.enumeration.devicewatcher.yml&version=GBlive&_a=contents
• Product: uwp
• Technology: winrt-reference
• Git Login: mcleanbyron
• Microsoft Alias: mcleans

[hanabanana]

Anyone can help with the clarification?

[mcleanbyron]

Thanks for submitting your feedback. I have reached out to the engineering team that owns this API for clarification, and will reply with an update when I have info to share.

[smadasam]

The Stop() method:

• Verifies the state transition is valid.
• Then, for each object type query, it closes the underlying query handle.

All query result actions that are already queued in the caller's process will fire the correct event handlers.

The device watcher is set to allow asynchronous handle closes. This means the WinRT client may asynchronously stop the watcher, and on some other API worker will be pumping results on another thread. If the client calls Close() while on the worker thread, The close event is queued in the result actions, and the worker thread continues to pump results from the queue.

[mcleanbyron]

I'm going to close this issue now that someone from the engineering team has responded. At a glance, it appears that the documentation is in line with the details in the response. If you feel the documentation should be updated, please feel free to reopen this issue with your suggestion, or feel free to click the "Edit" button in the article and submit your own pull request. Thanks for your feedback.