-
Notifications
You must be signed in to change notification settings - Fork 461
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
Windows doesn't get unminimized after "hide-all-normal windows shortcut" #134
Comments
I have been trying to reproduce this but I haven't been able to do it at all. I tested this on both 3.14 and 3.20. @micheleg can you reproduce it? |
Yes, on 3.14 (Debian Jessie). Set the click option to minimize and enable the hide all normal windows shortcut. Hide all windows and then try to click on the launcher. Nothing happens. Instead, with the cycle though window option it seems to work normally. |
Ah! I managed to do it now... I didn't have the bug as I use "Icons on desktop". Essentially focus was being given to the desktop, so technically not everything was minimized! |
I think I found out what the problem is.
I don't know that there is an easy way to fix this... The focus is not removed by the command (this seems fixed in 3.20, I don't know about 3.18, 3.16). |
I'm not sure when the change happened. Maybe https://git.gnome.org/browse/mutter/commit/src/core?id=6c05eb583e10293b9979cd254a77cf9ea02473b1 In any case, as a workaround, what about adding:
on line https://github.com/micheleg/dash-to-dock/blob/gnome-3.14/myDash.js#L1515? This should restore the default behaviour, which unfortunately is not optimal as it show only one window. Maybe we could add a check of this kind instead:
? |
Thanks for the suggestions! Using Can you test this on 3.14? As I said before, this doesn't happen on 3.20, but I don't know about 3.16 and 3.18. |
I've just updated my main machine to 3.20! I'll check on another system. I'm not sure right now if it is correct, but one problem that I see: what if I would also add comments to document the workaround (and maybe we can remove for Gnome Shell 3.20+) |
This reverts commit 571fc30.
I just checked the problem on other versions:
So apparently only 3.14 and 3.16 need to be fixed! |
I moved the fix in the activate function (https://github.com/micheleg/dash-to-dock/tree/fix_unminimization). It makes more sense there: the minimizeAllWIndoes function should always do what its name states. |
Sounds good. Do you want me to test the branch? Or we can call it done? |
I quickly tested it, but if you can test it further to double check it On Thu, 14 Jul, 2016 at 10:12 PM, franglais125
|
I had to apply a small fix [72a51ce]. I just added "this." where needed, and removed "settings" as input. This is actually my fault, the patches I linked in this thread are from a branch that had the workspace isolation implemented. I rebased my 'gnome-3.14' to yours, and then separated the other stuff in a new branch, as I use locally for 3.14! |
Ok, I updated the branch. |
It seems we are never done with this, but I think this is the last time I bring it up. Here is a small patch [7f09eec]. We are indeed checking that we don't get a null, but if |
I think you can safely unify the
|
Ah, didn't know, but suspected as much. I think the exact same fix works on 3.16 too. |
bad63r on the extension site says: "I don't know is this a bug or shold be like that but : when you make keyboard shortcut-navigation-hide all normal windows, and then you try to unminimize it via click on icon on dash it is not working(i'm talking when you have chaked option in dash to dock settings to minimize programs on clik on icons on dash)"
More info: It works with the cycle through windows option but not with the minimize on click option.
The text was updated successfully, but these errors were encountered: