attilah, sorry for the long delay. I didn't understand enough from your original reply to implement a solution. Other stuff came up and I put the whole thing on the back burner. But I'm now down to 'the short strokes' and need
to finally to get this solved. In the users eyes, it is a glaring deficiency that I don't display a waitcursor
It's still not clear to me where the cursor is actually getting set, in other words, in what class does the line "Mouse.OverrideCursor
= Cursors.Wait;" reside? Having the IClientMessageInspector publishing events to the eventaggregator implies to me that code that is calling a service would need to raise a Windows event rather than a CompositePresentationEvent.
And if that were the case, who subscribes to the CompositePresentationEvent that is published from the class that derives from IClientMessageInspector?
From what I can tell, I need a class that has both a reference to the eventaggregator and direct access to the Window. Our Shell.xaml.cs could do it if I could get the eventaggregator injected into it, but I don't see how the bootstrapper could accomplish
Prism (desktop) has got to have some means to support controlling the mouse cursor.
Thanks for any more clues you can provide.