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

Portable Mode #88

Closed
smaragdus opened this issue Aug 20, 2022 · 4 comments
Closed

Portable Mode #88

smaragdus opened this issue Aug 20, 2022 · 4 comments

Comments

@smaragdus
Copy link

As of version 3.7.4 Tag Editor saves its configuration file (tageditor.ini) in AppData:

C:\Users\User\AppData\Roaming\tageditor.ini

For fully and truly portable mode I suggest that when the program starts it checks its program folder (the folder containing the executable) for its configuration file (tageditor.ini) and if found it is used (settings are loaded from it and saved to it) without creating a new one is AppData. This will mean that Tag Editor is running in portable mode as it is not writing any data outside its program folder.

I suppose that this will not be hard to be implemented.

Off-topic- thanks to the developer (@Martchus) for offering Qt5 builds which means that I can still use the program.

Martchus added a commit to Martchus/qtutilities that referenced this issue Aug 20, 2022
* Keep handling for old location of settings file
* Add handling to allow portable settings (see
  Martchus/tageditor#88)
Martchus added a commit to Martchus/syncthingtray that referenced this issue Aug 20, 2022
Martchus added a commit to Martchus/passwordmanager that referenced this issue Aug 20, 2022
@Martchus
Copy link
Owner

Good idea, implemented on master.

Off-topic- thanks to the developer (@Martchus) for offering Qt 5 builds which means that I can still use the program.

Good to know that there are still users. I suppose I'll retain Qt 5 support for the foreseeable future (and also continue providing builds).

@smaragdus
Copy link
Author

@Martchus

Good idea, implemented on master.

This was impressively quick, thanks!

Good to know that there are still users. I suppose I'll retain Qt 5 support for the foreseeable future (and also continue providing builds).

This is excellent news for me. I will keep using Windows 7/8/8.1 as long as I can (I have even an XP machine for retro gaming). I refuse to upgrade to Windows 10/11 (for me this would be a downgrade actually) and there are both practical (1) and ideological (2) reasons for this: (1) using stable, heavily customized software that runs smoothly and is not endangered by buggy updates, features removal and heavy bloat is fun; (2) I refuse to accept adware, spyware and forced updates by M$, for me Windows 10/11 are an ugly, unbearable mess. I suppose that in the future I will have to switch to Linux or BSD and also learn to compile stuff myself (I am not a programmer but some days ago I had a peep at Lazarus IDE and I am glad that despite the intimidating interface I managed to compile my first program). I thinks it was a bad idea that Qt 6 had cut off Windows 8.1 support before the official OS support ended.

I did just a brief, superficial testing of Tag Editor, liked it and kept it. When I have time I will do some more thorough tests and if it happens that I can think of possible improvements or encounter problems I will let you know.

Thanks for your good tag editor and for the extended support for outdated Windows versions.

Regards

@smaragdus
Copy link
Author

@Martchus

I have just tested version 3.7.5 and it works as expected- the configuration file in program folder is accepted and used and no configuration file is re-created in AppData.

Good work, thank you for implementing portable mode!

You don't keep change log. don't you?

@Martchus
Copy link
Owner

Thanks. Regarding logs, there's only the Git log (but no condensed version). However, the commit shouldn't have been hard to spot in the Git commit log.

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

No branches or pull requests

2 participants