Itried the but on Opera that outputs a strange input box coupled with an "up and down" handler. What I expected was a regular text field that once you focus on it prompts the number keyboard instead of the alphabets. Is that even possible?
Beware: Using type="number" can cause problems with some browsers and user experience for credit card, postal code, and telephone inputs where a user might need to enter punctuation or a comma being in the output.
This post is now invalid. All smartphones support HTML5 and CSS3 now, so adding type="number" does in fact prompt the number pad to pop-up. I just checked it on 2 different Android versions, and an iPhone. Just so no one in the future tries WAP instead of the correct HTML5 format.
You can control the style of keyboard that comes up on input focus, independently of the input type, with the HTML attribute inputmode. What you're probably looking for is inputmode="numeric", which shows a number pad with 0-9. There are other options, such as a number pad with # and *. See the docs linked below.
This will work on mobile and will prevent the letter "e" (along with all other letters) from being allowed to be typed in in the desktop version of your page. type="number" by itself still normally allows "e" per spec:
I have a Windows 10 desktop and I use a mac keyboard with number pad on it. Its model number is A1243 and its connected by USB. However I cant seem to get the right driver or configuration to get the number pad to actually work. Any suggestions?
Turns out that the problem was pressing the numlock key. I managed to do that by starting the On-Screen Keyboard from Windows 10, turning on the numeric key pad in the options and then pressing NumLock there.
I'm using contenteditable in several sections of our time keeping app. Since we're logging time, naturally, I want the keyboard to automatically switch to the number keyboard for ipad users. I've tried adding all the attributes to the elements that I can think of such as:
I am not sure how you are using the keyboard here? Means, Is the user adding / Updating time or something? If they do, make the input type to number. This is will tell the browser (safari) that this is input for only numbers and it will tell the iOS to show number pad automatically.
This should give you the nice numeric keyboard on Android/iOS phone browsers, disable browser form validation on desktop browsers, not show any arrow spinners, allows leading zeros, and allows commas and letters on desktop browsers, as well as on iPad.
You could try 0000 as the pin in the first instance. If this fails to resolve remove all pairing records for your keyboard and download the latest drivers for your BT module from the BT manufacturers website.
Just was given this Keyboard for my Birthday. I ran into the same problem as Luba_LC_A, above. I have tried all the proposed solutions, to no avail. I will try contacting ANKOR as suggested by Shenoy, above. If anyone has found a solution in the meantime, please post here.
i just paired my keyboard very simple on your active keyboard when the pin window shows up put in 000000 and hit enter then on the anker keybaord type oooooo and hit enter t pairs right up hope this helps
If you found my answer helpful please say thanks by clicking on the Thumb's Up icon.
If my answer solved your problem please mark it as the Accepted Solution. Thanks!
Have an HP model 4BS28UA laptop. The dedicated key/number pad no longer works (e.g., 7 takes me "home", 8 takes me arrow up one, 9 takes me "page up", 3 takes me "page down"). I want to use the actual numbers. I've obviously hit a key combination to deactivate the numbers how can I get my numbers back? Thanks, P Winn
I just upgraded to 2015 where viewport 2.0 is now default however when I do a smooth mesh preview (number 3 on the keyboard) Maya crashes. I reopen and tested it in Legacy default viewport and hit 3 on a simple cube and it works fine, with that same cube in preview mode I switched back to viewport 2.0 and *crash*. I found someones post out in forums
After nearly 3 years on SCN, I'm finally posting my first question. I've been working on some lightweight Fiori-like apps, and I've ran into an interesting situation I haven't figured out yet. I'm still fairly new to SAPUI5 tools, so if what I describe is expected behavior I'll feel much better.
Here's the situation: The app I'm currently working on was developed in Web IDE following the MVC format. My view is in XML. The devices used are Android powered scanners and Windows desktops. I have an Input control for a material number. Although material numbers can be alpha-numeric, the users have requested to use numbers only in the control. SAP provides an easy way to do this by stating the 'type' to be a number.
Notice I also have a 'submit' event on the Input control so when the app detects an 'enter' from the user on the field, the controller will take the requested material number and perform a select on the SAP backend. This works perfectly fine on the desktops.
The problem is with the soft keyboard on the Android scanners. For reference, it's Android OS ver 4.1.2 (I have also observed the same behavior on my personal Android phone ver 6.0.1). The soft keyboard for the Android OS number pad does not contain an 'enter' key but instead has a 'next' key. The 'next' key does not trigger the 'submit' event on the Input control. What happens by default is the focus moves off the Input and to the next available control.
But this causes the soft keyboard to work incorrectly or not at all on the other input fields. I have also tried it using the 'onsapfocusleave' to the same result. Lastly, I've tried to attach the "blur" browser event which does not appear to work at all.
I had a similar problem not being able to react on that silly NEXT button. I find it peculiar that the numeric keyboard does not have an ENTER og RETURN key. But I managed to detect the NEXT-button-press and run code. The trick is to use the "onkeydown" function and scan for keyCode == 9 . The code below is used in the init of my Neptune app.
However, this did not solve my issue, which was updating my app with the input. Somehow the inputvalue did not come along through the binding. It seems the value from the UI-element did not yet update the binding-structure. I found no way to read the input value and could not use this. But maybe you find how to get hold of this ( I am a beginner in this field ).
The "onkeydown" function was a good idea. I hadn't tried that when I initially posted my question. I would suppose your app wasn't updating with the function because the binding wasn't detecting a triggering event, which is really where all our problems are coming from in the first place.
We deployed our apps on version 1.38.17 of the SAPUI5 build. Perhaps there is a more robust solution today on the most current version, but we haven't had to make any changes yet (although I'd love to upgrade).
For the IOS ten key keyboard, I thought it had a decimal point? If this was the case could the entry be parsed such that leading with a decimal would covert to a - value and anything else would record as a + entry? If RST 0 then -RST else +RST?
FYI: Ok it took awhile of messing around before I was able to get this MS SwiftKey KB working the way I wanted. But I have notice that it present a problem in the Landscape vs Portrait view. Portrait view is ok but in the Landscape view the KB covers a lot of stuff up. See Attachments.
Landscape17242302 401 KB Portrait16321106 226 KB
New iOS user here - love this app so far. If you want to see a model of what I hope for (on iPhone), take a look at the QRZ Callsign Search app. There, the alpha keyboard always shows a row of numeric keys above the letter area:
I hope this is appropriate for this forum, so here goes. I purchased a new HP laptop whose keyboard included a keypad. I loaded my MS 365 and when I use Excel the keypad won't work and I have to use the top row number keys. I can use the keypad for other programs but when I open Excel then the keypad stops working. I haven't been able to find a way to keep the number keypad on while using a program designed for working with numbers. Help!
Has anyone ever actually been able to trigger the keypress of a number pad key using the Keyboard.write commands from an Arduino? I can trigger keys like a-z, 0-9 fine, but I either cannot find the appropriate ascii/hex (despite many different results found on google that I have attemtped) or it just doesnt work. I have even tried the hex codes outlined by the USB organization ( _docs/Hut1_11.pdf) with no luck.
Look at the library source code (libraries/Keyboard/src/Keyboard.c). The first 128 (0-127) values are treated as ASCII and translated to US English keycodes through a lookup table. The next 8 (128-135) are the modifier keys (left and right Shift, Control, Alt, and GUI). Anything above 135 has 136 subtracted from it and then used as a raw USB HID page-7 key code. Because the byte can only hold values up to 256, only key codes up to 120 can be used. This is sufficient for a US English 101-key PC/AT keyboard but not for some keys on some non-English keyboards and various keys on extended keyboards.
Since yesterday, when I am in ESET, and only when I am in ESET, the number keys on both my laptop keyboard and also on the connected separate keyboard, malfunction such that the number shown on the monitor/screen does not correspond with the number-key I have pressed. This applies to both the number-keys along the tops of the keyboards as well as the number keys on the 10-key section on the right-hand side of the keyboards. It is somewhat random, but sometimes it just repeats the last number input from two to several times - and again, this occurs no matter what number-key I am pressing. Sometimes, the typing of a number-key produces a decimal point, although I have not touched that key at all.
3a8082e126