Hi,
I have an edittext field in my rollout with a “on edt_Test entered input do …” funtion in which the “input” gets processed. Everything works fine as long as I don’t try to enter something with the numpad of my keyboard. Once I tried to enter numbers with the numbpad the textfiled is “broken”. None of the processes within “on edt_Test entered input do …” get executed anymore. If I try to enter something with the main keys on my kexboard after using the numbpad, still nothing works. I can only close the dialog and restart it to get out of what ever the numpad caused.
Does anyone have some information about this or know how to handle this? Could I check for a numpad input in advance somehow?
Thanks,
Lena
That should work without a problem, lets see the code.
Thanks for the info, I just tested an old version of my code and the number pad works indeed just fine with that version. There is some weirdness going on with my code… I think the normal “Enter” key misbehaves now as well. Only entering a value into the text field with the “Tab” key works as intended.
I need to investigate some more…but I guess I will be back soon.
alright, I found the core of the problem (another classic…): through some copy and past I accidentally changed the textfield’s height to 20px, therefore it got an multi-line textfield and the “on entered” function didn’t work anymore. Why I earlier had the impression that the number pad solely didn’t work, I am not sure anymore.
have you bound any of your keys on the numberpad to any max shortcuts?