11-12-2010 10:45 AM
Hi Berezka.
I was able to reproduce this on a Hebrew windows 7 system and on an XP system setting Hebrew as the language for non-unicode programs. I think it's likely a bug in the ExpressionEdit control of TestStand. I created a bug report on this issue which should be fixed in a future version of TestStand. For your reference the bug report ID is 257891.
I also apologize for all the hoops you were asked to jump throuh on this issue and appreciate your patience with us.
11-14-2010 01:28 AM
Hi Jimmi,
Thank you very much!
12-10-2010 06:00 PM - edited 12-10-2010 06:05 PM
I looked into this issue and it looks like a bug in the underlying RichEdit control that the ExpressionEdit control uses. I was able to reproduce this in a simple scenario with a rich edit control. I filed a bug report to Microsot on this issue:
I don't think a work around is possible on my end, so we'll have to hope we get a fix from Microsoft.
I also noticed another behavior that seems a bit odd. If you have the current input language set to Hebrew and you press the Home or End key, the input language is set back to English. This also happens in a rich edit control. Is this another bug I should report to Microsoft?
01-21-2011 02:43 PM
Berezka -
Because we've identified this as a problem in the underlying RichEdit control that the ExpressionEdit control uses and we have no idea if or when Microsoft will fix this bug, we're considering implementing a "fix" to this behavior in TestStand. This "fix" would involve turning off the RichEdit control feature that automatically changes the Current Input Language based on the cursor's active character. This would prevent the behavior you are seeing but would also require you to manually change the Current Input Language to English whenever you want to type English text in the ExpressionEdit control and manually change the Current Input Language to Hebrew whenever you want to type Hebrew text in the ExpressionEdit control.
Would this be a reasonable solution for your use case?
01-23-2011 06:31 AM
Hi Manooch,
It seems to be a good solution.