hoffstadt / hoffstadt/DearPyGui
mvKey_Prior / mvKey_Next mapping issue
- Dominant language
- C++
- Stars
- 15.6k
- Forks
- 783
- PR merge metrics
- No merged PRs in 30d
Description
### Dear PyGui version:
2.3.1
### Python version:
3.14.5
### Operating system:
Windows 11 25H2
### My issue/question:
I was using Python 3.14.3 + dpg 2.2, but recently updated to Python 3.14.5 + dpg 2.3.1.
After that, dpg.mvKey_Prior and dpg.mvKey_Next stopped working.
Upon checking the cause, I found that while dpg.mvKey_Prior outputs the previous value of 33, the actual key value is 517.
Considering that dpg.mvKey_Up is showing 515, I suspect there might have been some omission during the mapping value change.
It is working fine now that I have switched back to dpg 2.2.
### Steps to reproduce:
1. add_key_press_handler
2. press key
### Expected behavior:
Events are triggered on Page Up/Down keys
### Screenshots:
N/A
### Standalone, minimal, complete and verifiable example:
```python
import dearpygui.dearpygui as dpg
def onKeyPressed(sender=None, appData=None, userData=None):
print(f"key pressed: {appData}")
dpg.create_context()
dpg.create_viewport(title='123')
with dpg.handler_registry():
dpg.add_key_press_handler(key=dpg.mvKey_Up, callback=onKeyPressed)
dpg.add_key_press_handler(key=dpg.mvKey_Prior, callback=onKeyPressed)
dpg.add_key_press_handler(key=dpg.mvKey_Next, callback=onKeyPressed)
print(f"mvKey_Up: {dpg.mvKey_Up}")
print(f"mvKey_Prior: {dpg.mvKey_Prior}")
print(f"mvKey_Next: {dpg.mvKey_Next}")
dpg.setup_dearpygui()
dpg.show_viewport()
dpg.start_dearpygui()
```
Contributor guide
Assessment
This issue has not been assessed yet.