This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello Jason: I'm using IntegerTextBox and NumericTextBox to get number input. But as our product faces to Chinese market, we got an issue which you may not see before. User has GooglePinYin (It's a Chinese input tool provided by Google) installed, then your IntegerTextBox and NumericTextBox does not accept the number input from GooglePinYin tool. Below are the steps to reproduce it: (1)Install GooglePinYin input tool. You can get it from: http://tools.google.com/pinyin/, Or from my cloud drive: http://1drv.ms/1QejooR (2)Place the cursor in the IntegerTextBox or NumericTextBox. (3)Select GooglePinYie as current input way.
(4)Go to GooglePinYin floating window like below, turn on the Chinese mode in GooglePinYin:
(5)Then input numbers by pressing on keyboard like usual.
(6)Like above, after input number 456, then click other place to make it lost focus, you'll see the number will be automatically changed into 0 and the border became red if you set the validation rule.
By the way for also, “Microsoft Pinyin ABC Input Style”, “Microsoft Pinyin New Experience Input Style”, these two are Windows built-in Chinese input ways, they also have the same issue. Could you help me on that, is there any settings or properties which I can set to resolve it? Or any other ways? This feature is really general and popular in Chinese operations. And also it's really urgent for the upcoming release deadline date. Thanks a lot. |
|
|
|
|
Hi Yaron, I will look into this for you early next week. -Jason Fauchelle |
|
|
|
|
Thanks |
|
|
|
|
Hi Yaron, I've had a look into this now. Unfortunately GooglePinYin is conflicting with the logic of our text boxes in a way that we can't do anything about. WPF provides a way to listen to when text is entered, and then see the state of the text box before any changes take place. This is the entry point to updating the model of our control. Here we do some checks about if the input is valid (e.g. it is a numeric character). PinYin is hijacking the input and causing the state of the text box to be updated before our event handler is called. This is causing the base WPF textbox code to behave in unintentional ways - forcing the text box to take whatever input it is given, and prevents us from updating the model correctly. I couldn't find any viable work arounds for this, as PinYin is inserting the text earlier than any events we can listen to. Sorry we can't be of more help here. -Jason Fauchelle |
|
|
|
