Textinput and backspace problem

318 views
Skip to first unread message

Filip Demaertelaere

unread,
Feb 19, 2017, 10:24:39 AM2/19/17
to Kivy users support
Hi,
I have a problem with the use of backspace on Android. It works fine on PC...
When I have a numeric textinput box and I type '4567' and then I use a backspace, the following text is ADDED to the textinput '456' with as a result '4567456'.
This is not always true, but playing around with typing and backspace results in similar situations where the backspace adds the previous text, minus the last character.
Eg typing '4567' and then two backspaces, gives '456745645'.
Has somebody the same problem?
I never have this on the PC, but always on Android. I am using kivy 1.9.0.
Thanks!
Filip

ZenCODE

unread,
Feb 19, 2017, 12:33:23 PM2/19/17
to Kivy users support
It's pretty important that keyboard behavior is clearly defined. So please post a complete, run-able example so we can test on different platforms. And when you say "You have a problem  on android", which android? How are you deploying? Which version? :-)

Sumit Madhwani

unread,
Feb 20, 2017, 3:59:59 AM2/20/17
to kivy-...@googlegroups.com
Hi Filip,
The same issue was some time before asked and I tested it. The problem is not with the tenxinput.py file. I think you would be using old toolchain for generating apk(`buildozer android debug deploy run`). I would suggest you to compile using new toolchain(`buildozer android_new debug deploy run`). I compiled it using both the toolchains and the problem was seen only in old toolchain. After consulting with the developer, the problem was actually in old toolchain.
Hope this helps!

 

On Sun, Feb 19, 2017 at 9:33 AM, ZenCODE <zenkey....@gmail.com> wrote:
It's pretty important that keyboard behavior is clearly defined. So please post a complete, run-able example so we can test on different platforms. And when you say "You have a problem  on android", which android? How are you deploying? Which version? :-)

--
You received this message because you are subscribed to the Google Groups "Kivy users support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Filip Demaertelaere

unread,
Feb 20, 2017, 10:36:25 AM2/20/17
to Kivy users support
Hi, thanks for this message.
I already tried the new toolchain and would like to migrate. I already tested it before. However, there are some recipes that I am using (like lxml) which are not migrated to the new toolchain. I once tried to do it myself, but couldn't sort it out. I still checked this weekend and seems that nobody added it yet.
Any idea how I can achieve this?


Op maandag 20 februari 2017 09:59:59 UTC+1 schreef Sumit Madhwani:
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+...@googlegroups.com.

Sumit Madhwani

unread,
Feb 20, 2017, 12:04:57 PM2/20/17
to kivy-...@googlegroups.com
Well for adding a recipe, if you are not able to do it then you can create a issue in python-for-android
repo. Maybe someone who can will help you.

To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+unsubscribe@googlegroups.com.

Oon-Ee Ng

unread,
Feb 20, 2017, 10:00:15 PM2/20/17
to kivy-...@googlegroups.com
An issue already exists (I raised it), but I found it easier just to port away from lxml to cElementTree. May or may not be possible for you based on how complex your xml code is, mine was pretty much a 2 line edit as even in lxml I was basically using the etree API.

Filip Demaertelaere

unread,
Mar 2, 2017, 2:51:27 AM3/2/17
to Kivy users support
Mmmm. Investigated a bit the cElementTree and did some testing with my code. I use lxml for parsing HTML (webscraping). Unfortunately there are a lot of problem with parsing HTML using cElementTree. So not really an option. Not yet clear how I will solve the problem to migrate to the new toolchain while using lxml. It is a pity that this library is no longer supported with the new toolchain. Seen it is an old topic, I suppose that it will not be done. Thanks anyway for the hints.

Op dinsdag 21 februari 2017 04:00:15 UTC+1 schreef Oon-Ee Ng:
Reply all
Reply to author
Forward
0 new messages