Messenger.Walk timeout is not applied to call

[mjanulaitis]

When calling Messenger.Walk the timeout is applied to each HasNext call which although appropriate is not applied to the loop around the HasNext call. The time should be applied to both each HasNext call and the entire loop.

[lextm]

By design. You can wrap up the call with your own timer, which triggers the necessary timeout you want.

[mjanulaitis]

That's all find and dandy but the task will continue to run. In my case I am walking a Windows machine which takes so long I have never seen it complete. The running task then consumes the CPU. It is never cancelled.