From 20cd789babdaf5edfc5f66033ff1701ad0d796bb Mon Sep 17 00:00:00 2001 From: Sam Lantinga <[EMAIL REDACTED]> Date: Sun, 5 Nov 2023 21:20:48 -0800 Subject: [PATCH] Improved migration documentation for the event memory change. --- docs/README-migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README-migration.md b/docs/README-migration.md index acddcf00b749..ab156c3e6545 100644 --- a/docs/README-migration.md +++ b/docs/README-migration.md @@ -298,7 +298,7 @@ The timestamp_us member of the sensor events has been renamed sensor_timestamp a You should set the event.common.timestamp field before passing an event to SDL_PushEvent(). If the timestamp is 0 it will be filled in with SDL_GetTicksNS(). -You should not call SDL_free() on the data in SDL_EVENT_DROP_FILE, SDL manages the memory for events internally, you no longer have to free the data yourself. +Event memory is now managed by SDL, so you should not free the data in SDL_EVENT_DROP_FILE, and if you want to hold onto the text in SDL_EVENT_TEXT_EDITING and SDL_EVENT_TEXT_INPUT events, you should make a copy of it. Mouse events use floating point values for mouse coordinates and relative motion values. You can get sub-pixel motion depending on the platform and display scaling.