Eisa01
"Free Up" a key locked/held by Script/LogManager?
In my input.conf, I have a keybind which is Ctrl+a which I use to cycle different aspect ratios, now when the LogManager is open and I press Ctrl+a it selects all the LogManager entries as it correctly should.
Now I want to use the ctrl+f keybind in input.conf for a different function but the trouble I seem to be having is, is that because the LogManager uses the ctrl+f keybind for activating/triggering the search, I cannot use the ctrl+f key with anything else, if I set a keybind in input.conf and I hit ctrl+f it does nothing, the keybind seems to be "locked" by the script.
I hope I'm making sense and being clear enough.
This is in SimpleBookmark or SimpleHistory?
The problem is with SimpleHistory, I tested this by taking each script out of the scripts directory and leaving the other one in and seeing which one caused the issue.
The problem with LogManager is that it has become outdated even with the changes introduced in SimpleBookmark.
Newer versions of mpv introduced many new features for developers, and now supports lists natively and inputs as well. It also supports history natively now (it's very limited in features though).
I have been developing features in "hacky" method for LogManager which is not recommended but was the only method applicable at the time.
Perhaps, I'll maintain such small fixes here n there, but I am not as excited to maintain LogManager as I was before. This is because I enjoy introducing simple stuff that are actually useful and feels native. That's why you are seeing more care towards the other scripts.
I think such small fixes are still possible and wont be much time consuming, I'll see what I can do to continue maintaining it for now at least.