The imgui adapter can deal with both variations of the char event (and minor-bump) (#772)

* The imgui adapter can deal with both variations of the char event

* also minor bump

Author: almarklein

CHANGELOG.md

@@ -17,6 +17,13 @@ Possible sections in each release:
 * Security: in case of vulnerabilities.
 
 
+## [v0.28.1] - 14-11-2025
+
+Fixed:
+
+* The imgui adapter can deal with both variations of the char event by @almarklein in https://github.com/pygfx/wgpu-py/pull/772
+
+
 ## [v0.28.0] - 10-11-2025
 
 We moved the implementation of the contexts to `rendercanvas` and made `GPUCanvasContext` lighter (and more low-level).

wgpu/_version.py

@@ -22,7 +22,7 @@
 
 # This is the base version number, to be bumped before each release.
 # The build system detects this definition when building a distribution.
-__version__ = "0.28.0"
+__version__ = "0.28.1"
 
 # Set this to your library name
 project_name = "wgpu"

wgpu/utils/imgui/imgui_renderer.py

@@ -229,7 +229,10 @@ def _on_wheel(self, event):
             event["stop_propagation"] = True
 
     def _on_char_input(self, event):
-        self._backend.io.add_input_characters_utf8(event["char_str"])
+        # There is an inconsistency in the keys of the char event between different rendercanvas backends.
+        # For the time being, we just consume both keys.
+        text = event.get("data", "") or event.get("char_str", "") or ""
+        self._backend.io.add_input_characters_utf8(text)
 
         if self._backend.io.want_text_input:
             event["stop_propagation"] = True