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

Disabling overwrite mode should permit same folder #64

Open
arsenyspb opened this issue Jan 2, 2025 · 2 comments
Open

Disabling overwrite mode should permit same folder #64

arsenyspb opened this issue Jan 2, 2025 · 2 comments

Comments

@arsenyspb
Copy link

It would be fantastic if, after I enabled the overwrite mode, I could disable it too, assuming the collision on filename is handled by filesystem or the app (e.g. adding a configurable prefix like _tiny). Thank you for the app!

@kyleduo
Copy link
Owner

kyleduo commented Jan 2, 2025

Thanks for your feedback.

The overwrite mode can be disabled in the Settings window. After disable it, the output images will be put into the output folder you set in the Settings window. Please leave a comment if you meet any trouble with this feature.

However, you provide another strategy that to configurate prefix (suffix maybe) to the filename and put the output in the same folder. I'll consider this strategy in feature list. Thanks very much.

@arsenyspb
Copy link
Author

My User Experience missed trying to use TinyPNG4Mac without enabling the overwrite mode (straight from installation, Out Of the Box Experience (OOBE)), only pasting the API Key). If the app is not allowing disabling the overwrite box without specifying the output folder, would it ask for output folder at OOBE too?..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants