We should either use the device virtual keyboard (which pops up) or use the gcompris one but not the two at same time. Pro of using gcompris' one: same for all activities in gcompris Con: having all layouts (with punctuation) for each locales may be really hard/long to do. Reproducible: Always
I'm not sure I understand this bug report perfectly, but it looks close to the enhancement request I was about to file. While using the "falling words" activity, the "keyboard" that pops up is in alphabetical order. Perhaps would it be nice to either allow the user to choose a layout, or at least use the system layout, rather than alphabetical order. I'm clueless about Android development (even Android use) so I have no idea about the feasibility. I guess the idea is that the default virtual keyboard for Android includes special keys we don't want here, and defining a virtual keyboard from scratch for each local would be a chore. (Sorry if this is unrelated to initial question...)
Hi, the bug is that for babymatch activity, we have both "android" and "gcompris" keyboards displayed at same time. For your point, for now, we use our keyboard, created from the different levels and sort them in the alphabetical order. We had some discussion about it (you can check the log in https://phabricator.kde.org/T1500). We can't just use the android keyboard (in case we use on linux with a touch screen for example) and I don't think we can change it to remove some keys easily (and depending on locales?). Another potential solution to explore would be to use the Qt virtual keyboard (http://doc.qt.io/QtVirtualKeyboard/) that will be released in Qt 5.7.
OK, I think I get the idea. Sorry for the noise.
No problem, it's a thing that we have to think of. I just don't know how we can solve the layout issues without having to redo all the layouts (which would take a lot of time...)
*** Bug 363159 has been marked as a duplicate of this bug. ***
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Still an issue. I'll see later if it is better to handle it as a phabricator task or a bug