In R2:875175c655dc7fdfbe0e937649b543cab55dcb82#2005359, @jjazeix wrote:

Does the images scale well when we have high/low resolutions?

The size of the ok button was decreased from 75 * ApplicationInfo.ratio
to 60 * ApplicationInfo.ratio. The height of the margin is decreased
from 20 * ApplicationInfo.ratio to 5 * ApplicationInfo.ratio, providing
more space for the instruction.

Number sequence: Some of the dots get hidden under the bar
(levels: 2, 4, 5, 7, 8, 9, mainly when the screen size is reduced)
https://bugs.kde.org/show_bug.cgi?id=357546

check() function now checks whether there is any ongoing check() call
or not. The check() call is over when the good/bad animation is over.
Turning auto-conversion is turned on/off via hint instead of
dialogActivityConfig.
Fixed Ok button overriding the instructions by adding virtual keyboard's
height

In D5444#105303, @jjazeix wrote:

In D5444#104539, @rudranilbasu wrote:

In D5444#104034, @jjazeix wrote:

the ok button can override the instruction. But I'm not sure how we can improve it.

Does the ok button override the instructions? I have added a Flickable to take care
of the condition of the instructions being too long. Does it still get overridden?

I am AFK for few days, I will check it to see if the problem still persists as fast as possible
and/or look for a better solution.

Here is the image: http://pasteboard.co/9rRnXjsuJ.png
It's not the smallest one we can get on Desktop but my "default" resolution

In D5444#104034, @jjazeix wrote:

the ok button can override the instruction. But I'm not sure how we can improve it.

In D5444#103760, @jjazeix wrote:

In D5444#103682, @rudranilbasu wrote:

Previously, the items.check() was called whenever any non-alphabet keys
were pressed. Most probably, the bug arose because it compared the
event.key with (Qt.Key_Enter | Qt.Key_Return). The bug is fixed now.

No, it's because the if was: if((key==Enter) || (Return)) and Return is always true because positive integer.

Previously, the items.check() was called whenever any non-alphabet keys
were pressed. Most probably, the bug arose because it compared the
event.key with (Qt.Key_Enter | Qt.Key_Return). The bug is fixed now.

Added checking answer via Enter and Return Key

Scrolling seems to work properly on windows 10 in my machine (both the configuration menu and the list of activities menu).
Additionally: GCompris seems to crash frequently on Windows 10. Not sure if this problem is specific to my machine only.
I will check it out on other Windows 10 devices to get more information about it.

An odd even category is added to the categorization activity.
Link - https://github.com/gcompris/GCompris-qt/blob/master/src/activities/categorization/resource/board/category_odd_even.qml