Skip to content
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

Quit Keka after Extraction #307

Closed
7s3 opened this issue Oct 15, 2018 · 19 comments
Closed

Quit Keka after Extraction #307

7s3 opened this issue Oct 15, 2018 · 19 comments

Comments

@7s3
Copy link

@7s3 7s3 commented Oct 15, 2018

Is it possible to have Keka quit after extraction?
I have the feature enabled that closes the app when there are no windows open, but unfortunately it doesn't do what I mentioned above.

Thanks!

@aonez
Copy link
Owner

@aonez aonez commented Oct 15, 2018

This might fix your issue:

  • Enable the "Close Keka when no windows are open" option in the Keka preferences
  • If already enabled, disable and re-enable it

From: #200 (comment)


@7s3 would be amazing if you can share with me the Keka preferences file so I can try to replicate this issue. It is located here:

~/Library/Containers/com.aone.keka/Data/Library/Preferences/com.aone.keka.plist

Just zip this plist file and upload it here.

Let me know if that helps.

@aonez aonez self-assigned this Oct 15, 2018
@aonez aonez added this to the 1.1.6 milestone Oct 15, 2018
@7s3
Copy link
Author

@7s3 7s3 commented Oct 15, 2018

I already had the "Quit after extraction" setting checked, but I toggled it off and on.
Maybe the setting wasn't sticking?

plist before:
com.aone.keka.plist.zip

plist after:
com.aone.keka.plist 2.zip

This feature seems to be working now, although it takes about 8 seconds for the app to quit after the progress box closes.

@aonez
Copy link
Owner

@aonez aonez commented Oct 15, 2018

Thanks @7s3! I'll test with the preferences file 😊

although it takes about 8 seconds for the app to quit after the progress box closes

This is a feature, so in case you click on the notification that appeared on Notification Center Keka can handle it properly. You can disable this feature though:
GrowlBlocksExit wiki/Hidden-configuration#notifications

@7s3
Copy link
Author

@7s3 7s3 commented Oct 15, 2018

Working perfectly now, thanks!

@aonez
Copy link
Owner

@aonez aonez commented Oct 15, 2018

Sadly the plists files are virtually identical, with the proper value set to quit. So, again as in #200, I'm not sure what is happening here. Will leave this issue open as a workaround for others.

@aonez aonez modified the milestones: 1.1.6, Look at Oct 19, 2018
@stale stale bot added the stale label Nov 11, 2018
@aonez aonez added the blessed label Nov 11, 2018
@stale stale bot removed the stale label Nov 11, 2018
Repository owner deleted a comment from stale bot Jan 20, 2019
@ghost
Copy link

@ghost ghost commented Jan 30, 2019

You can replicate the issue using some kind of app switcher that hides apps by default (Single Application Mode) or manually hiding Keka with H while the progress is up.

In my case, I found this issue using LiteSwitch X and when using Tab to switch to another app, I have it configured to hide all other apps, by default. So, switching away from Keka while it's compressing/extracting, is like hiding it and it doesn't quit automatically when finished (no ... badge on Keka's dock icon).

@aonez
Copy link
Owner

@aonez aonez commented Jan 31, 2019

manually hiding Keka with ⌘H while the progress is up

Thanks @MEGADR01D! Replicated this 👍

@aonez
Copy link
Owner

@aonez aonez commented Jan 31, 2019

@MEGADR01D can you check this build has this issue fixed: Keka-1.1.11r3251-autoquit.7z

@gingerbeardman
Copy link
Contributor

@gingerbeardman gingerbeardman commented Jan 31, 2019

Great to see this old one found and fixed!

@ghost
Copy link

@ghost ghost commented Feb 2, 2019

@MEGADR01D can you check this build has this issue fixed: Keka-1.1.11r3251-autoquit.7z

404

Do you mean https://github.com/aonez/Keka/releases/download/dev-test-builds/Keka-autoquit.7z

@aonez
Copy link
Owner

@aonez aonez commented Feb 2, 2019

Do you mean

Yes, updated the build but not the link here 😅

@ghost
Copy link

@ghost ghost commented Feb 2, 2019

@aonez No problem, man.
I'm glad to report that Keka-autoquit.7z works correctly and auto quits Keka whether it's hidden or not.

@aonez aonez modified the milestones: Look at, 1.1.12 Feb 4, 2019
@seajaysec
Copy link

@seajaysec seajaysec commented Feb 5, 2019

Keka won't close windows for me after decompressing no matter what. I've tried toggling "Close Keka When No Windows are Open", using the main branch download, using the dev "autoquit" branch listed above, and setting these two variables:

defaults write com.aone.keka GrowlBlocksExit -bool FALSE
defaults write com.aone.keka UseGrowl -bool FALSE

Kind of at a loss. I love how powerful keka is, but hate that it takes over my screen any time I unarchive something.

@aonez
Copy link
Owner

@aonez aonez commented Feb 5, 2019

@chrsjhnsn could you remove the Keka preferences (close Keka first) and try the Keka-autoquit again? If it works, you can delete the preferences again and try the stable version.

To remove the preferences using the terminal:

k='com.aone.keka'; rm ~/Library/Preferences/$k; rm -r ~/Library/Containers/$k;

If it does not work I'll make a custom build to get some logs, if it is ok.

@seajaysec
Copy link

@seajaysec seajaysec commented Feb 5, 2019

@aonez that didn't do it on its own, but helped get me there. after removing the prefs, Keka-autoquit was still not autoquitting. Rerunning the terminal boolean commands for toggling off Growl and for allowing Growl to block exit fixed it perfectly though.

Thanks so much. Amazing utility. Really glad it works so smoothly now.

@aonez
Copy link
Owner

@aonez aonez commented Feb 5, 2019

@chrsjhnsn glad it works now! Note that UseGrowl can be enabled/disabled in the Keka preferences, is the "Enable Notification Center integration" check. If this one is disabled, GrowlBlocksExit is ignored, because there will be no notifications to wait for.

If you have time to test, it will be interesting to see if enabling both UseGrowl and GrowlBlocksExit causes the issue again. Note that Keka waits about 5 seconds with GrowlBlocksExit enabled.

@ghost
Copy link

@ghost ghost commented Feb 5, 2019

@chrsjhnsn Starting from OS X Mavericks, I think, app preferences are cached and even after deleting them you need to reboot.
I suspect the Terminal hidden settings for Growl were not necessary, since I never applied them and the autoquit dev build worked just fine, out of the box.
For peace of mind, if you want to try it, delete all Keka preferences again, reboot and try the autoquit build again.

@aonez
Copy link
Owner

@aonez aonez commented Feb 5, 2019

@MEGADR01D you're right, I usually just kill the cfprefsd processes but restarting might be safer.

@aonez
Copy link
Owner

@aonez aonez commented Feb 26, 2019

Just released 1.1.12, @MEGADR01D your issue is fixed there. I'm leaving this one open anyway.

@aonez aonez modified the milestones: 1.1.12, How-to Feb 26, 2019
@aonez aonez closed this Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants