From c8e0312195eef4db3d0041755c0cc743cf5b5c4d Mon Sep 17 00:00:00 2001
From: Peter Hutterer <peter.hutterer@who-t.net>
Date: Thu, 8 Jan 2026 17:54:26 +1000
Subject: [PATCH] test: don't assign -1/-1 to x/y on proximity out

This only worked because any all our test devices declare a fixed 0
value for x/y in the proximity out event frame. Since 0 !=
LITEST_AUTO_ASSIGN we never got to the litest_scale() for x/y which
would abort because of the -1 value.

Part-of: <https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1398>
---
 test/litest.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/litest.c b/test/litest.c
index 7d950996..26fc2bb0 100644
--- a/test/litest.c
+++ b/test/litest.c
@@ -3001,7 +3001,7 @@ litest_tablet_proximity_out(struct litest_device *d)
 			litest_tool_event(d, ev->value);
 			break;
 		default:
-			value = auto_assign_tablet_value(d, ev, -1, -1, NULL);
+			value = auto_assign_tablet_value(d, ev, 0, 0, NULL);
 			if (!tablet_ignore_event(ev, value))
 				litest_event(d, ev->type, ev->code, value);
 			break;