Revert "console.lua: disable cursor autohide while selector is open"

[Dudemanguy]

In retrospect, this isn't so great because no neccesarily everyone would want the mouse to show with the menu and said menu can be navigated with the keyboard anyway.

This reverts commit a8f5beb.

[github-actions]

Download the artifacts for this pull request:

Windows

• mpv-i686-w64-mingw32
• mpv-x86_64-w64-mingw32
• mpv-x86_64-windows-msvc

macOS

• mpv-macos-13-intel
• mpv-macos-14-arm
• mpv-macos-15-arm

[hooke007]

The true reason should be that a script would never respect user's option...

[dyphire]

I think there could be an option to control this behavior. This would be useful in certain scenarios: if the cursor is automatically hidden the user has no way of knowing if the cursor is inside or outside the menu, which affects the action of the mouse after a click. There must be users who think this makes sense and need it.

[Dudemanguy]

We can always hammer out the details later if someone wants but for now let's just get this out of the way for the release.

[guidocella]

An option is not needed:

[cursor]
profile-cond=user_data['mpv/console/open']
profile-restore=copy
cursor-autohide=no

[verygoodlee]

An option is not needed:

[cursor]
profile-cond=user_data['mpv/console/open']
profile-restore=copy
cursor-autohide=no

I have used a similar auto profile before

This also affects the input.get(), it doesn't have any mouse keybinding,
expected behavior is to affect only the input.select().

And this will cause excessive spam msg on the console.

[guidocella]

We could add user-data/mpv/console/select then. Those applying auto profile messages are annoying in general, I disable them with --msg-level=auto_profiles=warn.

[guidocella]

Another option is to disable cursor-autohide only after the first MOUSE_MOVE. Else separated keyboard and mouse focus styles need to be implemented.