We are using version 11.2. Please provide a workaround in 11.2 if this issue is fixed for 12.1 as we are not in a position to upgrade the existing project to 12.1. I haven't tested for 12.1.

Hi,

It seems that this is a bug in our control. 

For now you can use SetFocuc() method inside try catch block. Looking for your reply if this workaround works for you.

Regards,

Anastas

HI,

 This issue has been resolved with the latest service release.

 Please let me know if you need further assistance regarding this thread.

 Sincerely,
 Matt
 Developer Support Engineer

HI,

  Create a method called SetFocusWorkaround for example, and invoke the automation element(which will be an argument of SetFocusWorkaround method) SetFocus method inside a ‘try-catch’.

So this will avoid a lot of ‘try-catch’ blocks.

For example:

public void SetFocusWorkaround(AutomationElement elem)

{

try

{

                elem.SetFocus()

}

catch

{}

}

And after that replace each usage of SetFocus method with – SetFocusWorkaround(maskedEditor).

Actually the SetFocus() method works partially – it set the focus to the maskedEditor, but after a second an exception is thrown.. So that’s why I suggest that you use this method inside a ‘try-catch’ block.

Sincerely,
Matt
Developer Support Engineer

HI,

I have logged this behavior in our internal tracking system with a Development ID of 118020. 
The next step will be for the developer to review this issue and offer a fix, or other resolution.

 Sincerely,  
 Matt
 Developer Support Engineer

Another thing I forgot to mention is that we are using Visual Basic for Applications for Automation scripts. Can you please specify whether the workaround that I mentioned above can be used in VBA. If yes, please provide some sample code.

Using the try-catch block won't work for me since the code is raising the exception everytime I call SetFocus(). Please provide an alternate workaround.

Also, when I focus the element using XamMaskedEditor.Focus(), it doesn't raise any exception and behaves as expected. This certainly means that the element can receive focus. Can you please provide me any possible explanation for this?

I tried to look into the Template of this control using ExpressionBlend. We can certainly extract the TextBlock(Normal Template) or PART_InputTextBox(Edit Template) and try to set focus onto these controls. But, this will require code changes at a lot of places. Please specify any other workaround to get this done.