![]() ![]() The way SlideIT works is simple: Touch the first letter of the word, drag it around to the others, and then lift up your finger at the end of the word. Many find this to be the fastest, easiest (and most fun) method of single-hand text entry. It works in the same manner as the more famous “Swype” software. If (m_DecimalKey || e.Ke圜har = Keyboard by Dasur is a replacement software keyboard that allows you to slide your finger around instead of tapping. Protected override void OnKeyPress(KeyPressEventArgs e) For example: protected override void OnKeyDown(KeyEventArgs e) We could add code to our application to track a decimal key and handle it differently. These applications may have special handling for this case. For example, both Excel and Windows Calculator both translate Keys.Decimal into a comma instead of a period. However, some applications do respond differently in French - Canadian settings. The regional input settings affects the behavior of the Decimal key. However, in the case of French - Belgian settings with the "Belgian (Comma)" input settings, Windows sends a WM_CHAR event with a comma. In the case of French - Canadian regional settings (with Canadian French keyboard), Windows sends a WM_CHAR event with a period when the user presses the number pad decimal key. Similarly, the OnKeyPress event is generated directly from the WM_CHAR event. WM_KEYDOWN is sending our application a Key.Decimal event. The OnKeyDown event is generated by the Windows WM_KEYDOWN event. NET to make this translation automatically. Is the globalization setting supposed to translate Keys.Decimal (number pad ".") into a comma automatically, or is our application supposed to change Keys.Decimal into the culture-specific decimal separator? I expected. Since the period is not a decimal separator in the current culture, the control reject this character. Our numeric controls handle number input in the OnKeyPress event. ![]() However, in both cases, the OnKeyPress event gives our control a period: Key OnKeyDown OnKeyPress The specific keystroke comes across in OnKeyDown. In OnKeyDown and OnKeyPress I see the difference between the keyboard period (Keys.OemPeriod) and number pad period (Keys.Decimal). I see the current culture and current UI culture are set to fr-CA. I switched my Windows regional settings to French - Canada and debugged our application. Our numeric controls are not doing anything when the user presses this key. A few years ago, we globalized our application, so users see the appropriate culture-specific symbols and translations.Ī French Canadian customer has asked us to change how our application handles the number pad decimal key. ![]() NET 2.0 Windows Forms application with lots of custom controls. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |