You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
brianlagunas[CodePlex] Hey, first of all, the BusyIndicator is great, and I am using it very successfully in my project. I thought I'd tip you off about one minor problem without though, luckily it is easy to fix.
nbsp
I put my UserControl inside a BusyIndicator and everything worked fine except that I noticed when I used the keyboard to tab out of the last control in my UserControl that the whole Window appeared to have focus. After using Snoop I was able to determine that
it the focus was in the Visual Tree of the BusyIndicator itself. I tried setting IsTabStop=False and Focusable=False on the BusyIndicator itself but that didn't fix it.
nbsp
I fixed it by changing the BusyIndicator's ControlTemplate, specifically I added IsTabStop=False and Focusable=False on the ContentControl that is named quotcontentquot. Then my app's keyboard navigation was back to normal.
nbsp
Just a heads up, thanks again for all your work.
nbsp
Josh
The text was updated successfully, but these errors were encountered:
brianlagunas[CodePlex] You were right. This issue was re-introduced into the .NET 4.0 version, but remains corrected in the .NET 3.5 solution. I have re-fixed it.
brianlagunas[CodePlex]
Hey, first of all, the BusyIndicator is great, and I am using it very successfully in my project. I thought I'd tip you off about one minor problem without though, luckily it is easy to fix.
nbsp
I put my UserControl inside a BusyIndicator and everything worked fine except that I noticed when I used the keyboard to tab out of the last control in my UserControl that the whole Window appeared to have focus. After using Snoop I was able to determine that
it the focus was in the Visual Tree of the BusyIndicator itself. I tried setting IsTabStop=False and Focusable=False on the BusyIndicator itself but that didn't fix it.
nbsp
I fixed it by changing the BusyIndicator's ControlTemplate, specifically I added IsTabStop=False and Focusable=False on the ContentControl that is named quotcontentquot. Then my app's keyboard navigation was back to normal.
nbsp
Just a heads up, thanks again for all your work.
nbsp
Josh
The text was updated successfully, but these errors were encountered: