marcohu

I think the desktop is shown this way: https://github.com/GNOME/mutter/blob/master/src/core/screen.c#L2466 Maybe it is possible to listen on the root window (global.gdk_screen.get_root_window()) for the property change?

There is an open PR that allows one to disable the buttons altogether (https://github.com/deadalnix/pixel-saver/pull/70), but it's already been available for quite some time and I'm not sure whether it will...

+1 An option to choose whether the buttons should be added to the top panel would be really nice. @pvsomebody Simply uncommenting the hooks for the buttons in extension.js seems...

Do you remember any specifics? Diffing 1.5 against master, I only found 3 breaking changes (setting text of appmenu, button theme loading and a window signal that is no longer...

Understood. I will create a new branch for 3.14 then. Thanks for your willingness to ship an update here as well. BTW, are there any statistics available about the usage...

The extension repository is still in beta. Maybe one day... FYI, I haven't uploaded any code yet, but dabbled a bit with screencasting tools and updated the README. I'm not...

As I said the differences are fairly small, that's why a versioning approach seemed reasonable to me. Are you planning to push a new 3.14 compatible version tonight? I'd have...

I'm already running a fixed version locally... But this issue certainly warrants attention. I can do a PR with these fixes synced from upstream. Then you (hopefully) just have to...

See #69 for the PR. I did not cherry-pick, but used Meld to locate the diffs and then committed the changes one by one. Less work this way.

Test case: - disable Pixel Saver - Reload GNOME-Shell (Alt+F2 r) - Start Meld - Create two files pal.txt and pal1.txt - Compare these two files with Meld - Start...