-
Notifications
You must be signed in to change notification settings - Fork 4
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
Attempt to fix unfocus. #6
Conversation
Well, this does not seem to work @elcste. I'm not sure I understand why it's broken or what to do to fix it then :( |
I tried it too and it also didn't work for me :-/ My original extension was already at the edge of my js abilities, so I don't have anything to add. I want to consider it more, but right now I am used to the original hiding behavior and much prefer with the focus preserved. (Not to mention the original code is much simpler, which means less likely to break with GNOME updates.) So I would like revert back to my original version and change the description not to claim the timeout is 5 seconds ;-) If you prefer your version with the fixed timeout, I'd suggest you submit your fork to EGO. I would add a link to your version for those who want that trade-off. I looked like incorporating PR #2 to add a timeout time preference wouldn't be too hard as well. Then we end up with two version people could choose from: my original, simpler version and a more complicated one with better timeout behavior but the caveat with focus. |
Considering that I have been unable to preserve the original behaviour wrt focus, I'm very okay with the reversion. I don't think it is a good idea to submit my fork to EGO though, as it is an obvious way towards confusion for everyone. Instead, I can offer to maintain an 'official branch' This avoids duplicating the extension and having to invent/deal with variations around the name |
That sounds good. I'm a fairly beginning git user so maybe you can heklp. Do you see any problem with me just creating a new commit to go back to my version? And then I can create the new branch and merge your PR in that. |
Uh, nope, this is not the usual way to proceed, and it'd duplicate the version reverted ^ ^" The best option here might be to rebase the
(also I've just noticed the I do know enough of git shenanigans to help you with this, but I'd need push access to this repo + permission to force-push on the main branch. Alternately, I can craft a mirror of all required commits/tags/branchs on my fork and then help you click the right buttons in order to import them here. You tell me :) |
I decided to do what I could personally easily understand, even if it was not optimal. To do as you suggested above, you can create a PR and then I can create a new branch |
Sure, I understand that you prefer not to rebase. Do whatever you're confident with, then I'll rebase my timer fix on top of that and PR it against branch |
There you go #7 ;) |
|
@iago-lito The Reopen button has is disabled with the message The unfocus brand was force-pushed or recreated. :-( |
Here is an attempt to fix the focus problem introduced by #3. FWIU, calls to
inhibit_unfocus()
anduninhibit_unfocus()
need to be exactly matched (?). This modification takes care of that. Maybe this'll solve the problem?/!\ WIP I haven't actually tested it yet. I'll test it asap.