i just downloaded the matchbox-keyboard - module, which works absolute fine for me. The problem is, that I only need the numbers (0-9) of the keyboard. Is there a possibility remove all the other Buttons?
thanks for your help
Related
Solved, see below!
Is there a way to reset keyboard layouts in general in Windows 10?
I messed up using Microsoft Keyboard Layout Creator some time ago, and I'm not able to fix it.
This is NOT something that can be fixed through anything in Language preferences, btw.
Last year, I was stupid enough to try to fix my keyboards on a "lower level".
I use the Norwegian and Korean keyboard a lot, sometimes also Japanese and Canadian French.
I have a hard time using symbols, like ";" - "'" - "~" etc, since these are placed differently on the various keyboards.
I looked for a solution, and found "Microsoft Keyboard Layout Creator". I tried to fix the keyboards, but it didn't work that well since it had problems with the Korean keyboard. I thus tried to change the Norwegian keyboard somewhat, so that I would be able to write more efficiently, without always checking what keyboard I was using (the Korean one also has the American one ingrained, with a simple push of Alt-Gr).
I also have tried to make a shortcut to go from Norwegian to Korean and back seamlessly, without scrolling through other keyboards as well (Win+Shift scrolls through all available ones).
I don't remember exactly what I did, but it didn't really work out, so I thought I deleted the customized keyboards, and went back to the regular ones.
But there was a problem: one of the keys, VK_OEM_3, the one to the left of "L" to be exact, (";" on a regular US kezboard) no longer worked in Norwegian when used in a regular way. At first, it changed keyboard every time I used it to write regularly. I had set it up to do this when pushed WITH another key (probably AltGr), but something was not right.
I managed to delete the customized keyboards, deleted and reinstalled the Norwegian keyboard from Microsoft, but lo and behold, the key no longer worked. I.e, it works when I push it down for a long time, maybe half a second, and then I get a lot of "øøøø". When using TeamViewer, it dosn't even help to hold the key in for a long time. And the digital keyboard certainly does not work.
I have tried to download other keyboards, and the key works well for A-Z and symbols that exist on a US keyboard.
Thus, the French keyboard, where it is an "M", works well. As does US and Korean keyboard layouts where it is an ";".
But it works as badly for Danish layout, where it is an "Æ" or German layout, where it is an "Ö". Both of these layouts were downloaded for the first time after I had messed up.
I have tried kbdEdit, that made me end up with a German keyboard layout I had a hard time to get rid of, even though I deleted it multiple times from "Langauge preferences".
I haven't learned kbdEdit well though, so it might work out.
But I'm afraid that it might not work, and that I
But what has happened here? I used a Microsoft program, and thought that would be safe enough, even though I was warned it might not work, since it's old. But messing up one key completely...
I have deleted all the new keyboards from the Registry (HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Keyboard Layouts), btw. But it's apparently on a lower level than this, since there are problems with all kinds of keyboards that have "extended Latin" letters on that place.)
What I wonder, is if there is a file that can be replaced with a standard file. I don't really want to reinstall Windows and my hundreds of programs, but I can hardly work in Norwegian the way things are now.
I have to check the phrases for eventual missing "ø", and when I remember the problem, it stops my flow since I have to push down for a long time and then delete the extra "øøø"s.
I finally managed to fix the problem:
Under registry keys, in my case in multiple locations, there is a map called SYSTEM\KeyboardLayout\Substitutes.
I deleted everything but the default one in all of these, and now it works!
I was opening my pc with a password and noticed that the letters of the keystrokes did not appear in the password-field. It made me suspicious if a key-logger 'snatched' my password.
Opening the pc with a password is a spine reaction, so I went back to check how much would be needed to miss a proper lock-in .. I'm sure enough to proceed to question you here.
Would I in the first place notice, if someone used a keylogger on me? Is letters not appearing in the text-field symptomatic for the use of a key-logger against me? If yes, do I have any chance of finding the key-logger to delete it from my pc?
I've written plenty of appropriate code (opengl + glfw) to suggest, that the keylogger would have to work as a service (added with administrator-credintials?) and be turned on at pc-start to do it's job, but I don't have a clue more than that.
letters of the keystrokes did not appear in the password-field
It could be a scenario; maybe the textbox was out of focus while you were trying to login. Because I beleive that keylogger won't hinder the keypress of a textbox.
According to my experience of getting hardware-input it would seem to be a slim case not to reveal it in a stelthy situation - you must be right.
during playback I run into an issue:
uIEMailAdresseEdit.Text = this.BasisWeb_0_Anmeldung_Zugangsdaten_SetzenParams.UIEMailAdresseEditText;
In my scenario I have users with an email address like this "user#data.com". If the "#d" is typed in, the file menu of Internet Explorer is opened (german Version: alt + d is the same shortcut as alt + f in english Version).
My testrun crashes at this point. Of course I could use other email addresses, but this is not an option for me.
I'm using Windows 7 64bit and Visual Studio 2015 Enterprise Update 3.
Any ideas?
Best regards
benny
Benny,
Setting the text does enter the string in character by character but I do find it mysterious that you're having this issue. I've entered hundreds of random email addresses in this way and never had keyboard shortcuts pop up. I'd try four things:
Before changing the text of the control object, make sure that you've set the focus on the object.
Ensure that the parameter text you're trying to send to the control object is a literal string.
Try using "Keyboard.SendKeys" directly. To me this seems counterintuitive, in my opinion you should only be seeing this issue when using Keyboard.SendKeys, not when setting the text directly.
Do some substring Voodoo. IE send the substring before the '#', then the '#', then the remainder of the string. This is ugly but 100% should work.
If you end up resolving the issue, please let us know!
I hava a java project that works with jsf and has many rich:suggestionbox. They are working good but I need them work after I enter 4. character to inputbox. The list that retrieved is too long and waiting too much. Do you have a solution for this issue?
Set minChars="4" to your suggestion box.
I'm using Unity3D and I'm having issues with the keyboard when I 'build' the project.
When I run the game within the Unity Editor, the input works fine. However, when I build the project and test it, I have no directional input whatsoever. The mouse works fine, the game registers keystrokes (the Esc key works), but the player won't move.
I'm using Input.GetAxisRaw("Vertical") and Input.GetAxisRaw("Horizontal")
I researched the issue on the web, but I'm still stucked. The only solution I found (in various links) mentions a problem with DirectInput and states that you should remove the key "Input" from [HKEY_CURRENT_USER\Software\Unity\Player], in the Windows registry, but that doesn't seem to work for me.
Has anybody else fought this problem? Any working solutions? Am I doing the registry trick wrong?
You should check out Input Manager in Edit->Project Settings-> Input. Have you tried using GetAxis instead of GetAxisRaw? I also suggest using, eg: Input.GetKey(KeyCode.A) and etc.
I've figured out what was troubling me.
Input.GetAxisRaw("Vertical") and Input.GetAxisRaw("Horizontal") were fine the whole time. Somehow, there was some code in the script that in the Editor worked just fine, but when running as standalone gave me a calculation equal to 0 (it depends on the Delta Time, so I assume that the Delta Time when running compiled is much smaller than when running in the Unity Editor) and thus the character didn't move at all.