Overlay.Visibility / Canvas usage in the SL Demos

Gareth posted on Tuesday, September 22, 2009

I've been using the Canvas and Overlay.Visibility technique employed in the Demos to stop any interaction with the user interface whilst an async operation is happening.

I've noticed that whilst this does stop any mouse click interaction it does not stop keyboard interaction and you can merrily enter characters and tab to other fields when the canvas is overlaid.

Has anyone else noticed this or have I got a problem with my implementation?

Gareth.

sergeyb replied on Tuesday, September 22, 2009

I have used a similar technique, and I had to do a couple of extra things for my "busy curtain". I had to set focus to it via Dispatcher.BeginInvoke(()=>{curtain.Focus();}) and (sometimes) I had to set TabNavigation to KeyboardNavigationMode.Cycle to keep tab key from going back to the main screen.

Sergey Barskiy
Principal Consultant
office: 678.405.0687 | mobile: 404.388.1899

Microsoft Worldwide Partner of the Year | Custom Development Solutions, Technical Innovation

-----Original Message-----
From: Gareth [mailto:cslanet@lhotka.net]
Sent: Tuesday, September 22, 2009 8:06 AM
To: Sergey Barskiy
Subject: [CSLA .NET] Overlay.Visibility / Canvas usage in the SL Demos

I've been using the Canvas and Overlay.Visibility technique employee in the Demos to stop any interaction with the user interface whilst an async operation is happening.

I've noticed that whilst this does stop any mouse click interaction it does not stop keyboard interaction and you can merrily enter characters and tab to other fields when the canvas is overlaid.

Has anyone else noticed this or have I got a problem with my implementation?

Gareth.