Mouse interaction breaks after using touchscreen on Windows touchscreen laptop

[AnseloOriginal]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When using GDevelop on a touchscreen laptop (HP model), interacting with the editor via touchscreen causes multiple UI and mouse-related issues. After any touchscreen input, normal mouse functionality becomes broken or inconsistent.

Steps to reproduce

1. Open GDevelop on a Windows laptop with touchscreen support (e.g., HP ProBook 11 G1 EE).

2. Interact with the editor using touchscreen input (for example, touching the event sheet or scene editor).

3. Try to continue using the mouse afterwards.

GDevelop platform

Desktop

GDevelop version

5.4.244

Platform info

Details

Device HP Probook x360 G1EE

Additional context

After the touchscreen is used even once:

• Scene Editor stops responding properly to mouse drag or pan.

• Events can no longer be dragged or reorganized with the mouse.

• Object dragging becomes impossible — objects “stick” or move unpredictably.

• Scrollbars vanish completely in the scene editor.

• Clicking an event opens it instantly instead of allowing selection.

• Switching back to mouse input does not restore normal behavior until GDevelop is restarted.

This happens consistently and severely impacts usability on touchscreen laptops.

[ClementPasteau]

At the moment, GDevelop considers a full screen to be either touchscreen or using a mouse. (not both)
The logic is here: https://github.com/4ian/GDevelop/blob/master/newIDE/app/src/UI/Responsive/ScreenTypeMeasurer.js#L4-L40

I agree this isn't ideal, I think the reason is that the interactions need to be handled completely differently in the code.
And I assume it's hard to switch between one and the other during a session.

Something to look into

[AnseloOriginal]

I suggest adding automatic switching between touch and mouse input. You can detect the input type using Pointer Events — specifically the pointerType property (e.g., "mouse", "touch", or "pen").

This would allow smoother interaction.

A current workaround is to disable touchscreen in Device Manager before using Gdevelop but this is a painful process.

[AnseloOriginal]

Alternative idea:
Instead of switching dynamically, GDevelop could lock the input mode to the first detected input (touch or mouse) when the app starts.

For example, if the user’s first action is a touch event, GDevelop runs in touch mode for that entire session. If it’s a mouse click, it stays in mouse mode. Pen inputs can be ignored.

This would reduce instability on hybrid devices, where an accidental touch currently breaks mouse behavior.