Numpad 5 is not mapped to Qt::Key_Clear

When building Qt 6.5.3 for QNX 7.1 x86 from source, you will notice that with this build, the keypad number 5 always registers as Qt::Key_5 whether Num Lock is off or on.

This results in a UI application being unable to disable the numpad key number 5 when Num Lock is off. All the other numbers (0-9) except for 5 work properly; when Num Lock is off, all the other numbers are not functional as numbers.

Test in Qt for QNX:

Check for key press event (Qt::Key_5)

1. When Num Lock is off and I press numpad key number 5, it detects Qt::Key_5.
2. When Num Lock is on and I press numpad key number 5, it detects Qt::Key_5.

Check for key press event (Qt::Key_Clear)

1. When Num Lock is off and I press numpad key number 5, it does not detect Qt::Key_Clear.
2. When Num Lock is on and I press numpad key number 5, it does not detect Qt::Key_Clear.

Therefore, there is no Qt::Key_Clear mapped. According to the Qt documentation, Qt::Key_Clear should be mapped to numpad key number 5 as the alternate function when Num Lock is off.

Test in Qt for Windows:

Check for key press event (Qt::Key_5)

1. When Num Lock is off and I press numpad key number 5, it does not detect Qt::Key_5.
2. When Num Lock is on and I press numpad key number 5, it detects Qt::Key_5.

Check for key press event (Qt::Key_Clear)

1. When Num Lock is off and I press numpad key number 5, it detects Qt::Key_Clear.
2. When Num Lock is on and I press numpad key number 5, it does not detect Qt::Key_Clear.

Therefore, in Qt for Windows, Qt::Key_Clear is mapped and functions as documented.