uosc's compatibility with other scripts.

[WhoMI7]

Some scripts have the tendency to break uosc's functionality, example: can't click on buttons, volume slider or uosc menu.
Is there any particular reason why?

Here is an example: MPV-Watch-Later-OSD-Menu, if I add this to my scripts, and scroll on timeline the volume changes with volume bar hidden.
And if I delete the script, it works just fine.

[NormTurtle]

i have experienced that too
uosc getting broken

[christoph-heinrich]

Are you on the latest uosc commit? There has been a similar issue recently #495

[WhoMI7]

Yeah. But maybe being on entirely different osc might be the problem. Like JKubovy here said.
And if not using default osc is the problem then using any script which was written without having uosc as reference will not be compatible. Ultimately making uosc incompatible with every other script out there.

[christoph-heinrich]

I've tried installing that script and uosc still works fine for me. I've also had a glance at it's source code and didn't see anything that could possibly cause that.
FWIW I've never had any compatiblity problems between uosc and other scripts before.

[tomasklaen]

I've skimmed through the source code of that script and haven't noticed anything obvious.

Are you sure you are on the latest uosc? There was an issue where using autohide would un-register cursor events listeners after a while.

[hooke007]

Apparently you manually create this bug.

# check your conf
key_moveup=UP Wheel_Up
key_movedown=DOWN Wheel_Down
key_movepageup=PGUP
key_movepagedown=PGDWN
key_movebegin=HOME
key_moveend=END
key_playfile=ENTER MBTN_LEFT

Different scripts use the same dynamic/force keybindings at the same time.
I have seen you were using a complex and hacky binding system while there are plenty of keybindings you had set (or created by those scripts). So it's easy to meet with keybinding-conflicts.

[WhoMI7]

Different scripts use the same dynamic/force keybindings at the same time.

Aren't they activated only when their respective menu is active?
Can't see them replacing keybinds in Active key bindings until their menu is activated?
But if it is the only possible reason, I can change the keybinds but to what extent? Just from the scripts-opts or input.conf too?
And is using Wheel_UP, Wheel_DOWN for changing volume, scrolling menus (uosc or other) such a bad idea?
And let's say I use Wheel_UP and Wheel_DOWN for volume, ; and ' for menu scrolling, wouldn't this be actually complex?

[hooke007]

I have seen you were using a complex and hacky binding system

Here is the keypoint. Only use these two scripts and then no issues. It must be something else make them work at the same time.

[NormTurtle]

Only use these two scripts and then no issues

this litrallyl breakes the usage of mpv as we use it
the hackable player

[hooke007]

Cannot get your point. If you only need the functions the two scripts provided, then just use it. Nothing unreasonable here.