[gcompris] [Bug 359527] baby_wordprocessor virtual keyboard

2022-10-22 Thread Jazeix Johnny
https://bugs.kde.org/show_bug.cgi?id=359527 Jazeix Johnny changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO

[gcompris] [Bug 359527] baby_wordprocessor virtual keyboard

2022-10-20 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=359527 Justin Zobel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED

[gcompris] [Bug 359527] baby_wordprocessor virtual keyboard

2016-05-16 Thread André Marcelo Alvarenga via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359527 André Marcelo Alvarenga changed: What|Removed |Added CC||alvare...@kde.org

[gcompris] [Bug 359527] baby_wordprocessor virtual keyboard

2016-03-13 Thread Jazeix Johnny via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359527 --- Comment #4 from Jazeix Johnny --- 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...) -- You are

[gcompris] [Bug 359527] baby_wordprocessor virtual keyboard

2016-03-13 Thread Jérôme via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359527 --- Comment #3 from Jérôme --- OK, I think I get the idea. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.

[gcompris] [Bug 359527] baby_wordprocessor virtual keyboard

2016-03-13 Thread Jazeix Johnny via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359527 --- Comment #2 from Jazeix Johnny --- 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

[gcompris] [Bug 359527] baby_wordprocessor virtual keyboard

2016-03-13 Thread Jérôme via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359527 Jérôme changed: What|Removed |Added CC||jer...@jolimont.fr --- Comment #1