Files
test2/source/blender
Campbell Barton d6fef73ef1 WM: Remove ASCII members from wmEvent & GHOST_TEventKeyData
The `ascii` member was only kept for historic reason as some platforms
didn't support utf8 when it was first introduced.

Remove the `ascii` struct members since many checks used this as a
fall-back for utf8_buf not being set which isn't needed.
There are a few cases where it's convenient to access the ASCII value
of an event (or nil) so a function has been added to do that.

*Details*

- WM_event_utf8_to_ascii() has been added for the few cases an events
  ASCII value needs to be accessed, this just avoids having to do
  multi-byte character checks in-line.

- RNA Event.ascii remains, using utf8_buf[0] for single byte characters.

- GHOST_TEventKeyData.ascii has been removed.

- To avoid regressions non-ASCII Latin1 characters from GHOST are
  converted into multi-byte UTF8, when building X11 without
  XInput & X_HAVE_UTF8_STRING it seems like could still occur.
2022-07-14 15:59:19 +10:00
..
2022-07-08 09:48:49 +10:00
2022-07-11 10:38:04 +10:00
2022-07-04 15:26:57 +10:00
2022-03-16 11:58:22 +11:00
2022-07-12 16:58:04 +02:00
2022-07-11 10:38:04 +10:00
2022-07-13 16:25:57 -04:00
2022-06-30 12:14:22 +10:00
2022-05-17 15:34:02 +10:00