-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right click doesn't register above OSC #20
Comments
Yes and no. This area is a the top end of the OSC controls layer (count the title, even if hidden). It should change if title is hidden. Will fix. |
Could you try this version and see if it's fixed in it, please: This is a dev version, if you notice any other bugs other than the already opened issues, please let me know. |
I tested with 5930340 and can still reproduce :( |
Could you try again please, I reverted a bit of code. |
PowerToys_GsNGuHPs4T.mp4blue dot is my right click; you can see where it works and doesn't |
Does it work properly for you? @Samillion |
It works exactly as you shown on the last video. I've reduced the deadzone above the OSC, so that once you reach the alpha fade, you're in "controller" zone. If that makes sense (ie: show osc). |
Oh I see. i guess I expected it to work like the stock OSC, where your inputs will register even 1 pixel above the OSC like below. in modernz there is approx 65 pixel gap where inputs don't work, but since the stock OSC doesn't have any fade, I suppose this makes sense why it works differently. PowerToys_ayVjPdro1B.mp4 |
Can always improve it to be exact and count the deadzone based if title above OSC is shown or not. Noted, though this might take a while, since the other things have been driving me mad 🥲 |
I've decreased the show/hide area above OSC a bit, now it should only create that OSC layer once the mouse is actually inside the top of the fade. Should I decrease it more or is it good as is? Review change in: 7d1d817 |
Nice, it has definitely improved things. My only concern is if someone were to use |
In the case that it's difficult to fix, can always ship it the way it is. It's not hurting anybody and users can adapt to how it works |
I can make it so that it uses the So that only when you hover the mouse in the line the title would be, it shows, anything above it is unaffected. The main purpose for that deadzone is: the title is functional. A very niche/specific function, that I personally never use, but exist in almost all OSCs, even stock. Title above seekbar function:
|
Cool, I'd be willing to test it. I can understand the title should stay functional. I just thought it was weird that the control layer counted the title even if it was hidden (like you said earlier) haha. |
I'll tinker with it a bit later, and I'll try to utilize your idea of based it on OSCfadealpha and existence of title. |
Ok, now that all the other issues are fixed and release of v0.1.2 is done (you're mentioned there btw), I'll focus on this to try and improve it. I still haven't thought of the best way to do this, because alpha shade is non-linear. Once I do though, I'll apply the changes. |
That's wicked man! Thanks for all these updates I think the script is pretty much bullet proof at this point. Should make it into mpv project one day (fingers crossed) 😆 |
Ok, back to this since I have some time to focus on it. Suggested solution:
Would that be an acceptable solution? |
Sounds good to me! |
I'll also add a user_opt to adjust the value of bottomhover (at the moment it's 160). That way, you can refine it to your exact liking. |
In the screenshot, the space between the seekbar and my mouse cursor acts like a dead zone where right mouse click won't do anything to pause/unpause.
The text was updated successfully, but these errors were encountered: