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

Feature Request: Remove all Config-Items from Windows registry #3862

Open
Nedorus opened this issue Sep 12, 2019 · 4 comments

Comments

@Nedorus
Copy link

commented Sep 12, 2019

Sorry for re-creating this Feature request again but I cannot re-open the first one.
This is NOT a duplicate #3532 even though they are somewhat related. However #3532 only considers custom data files / directories for different playing groups. This request however aims at improving overall portability of Chummer across multiple installations.
I have removed from this Feature Request any reverences to sharing between playing groups with different settings etc. as that was not the main focus of this issue. Also I have removed the idea of splitting settings in any way as I understand that ALL settings should be global. But imho even global stuff should - as a general rule - not be stored in the Windows registry as that make application non-portable and less maintainable.

Is your feature request related to a problem? Please describe.
In case of using a shared installation (e.g. running Chummer from a Google Drive) options changes often need to be made across multiple machines because many option items (e.g. the enabled books) are stored in the windows registry.

Describe the solution you'd like
All options should be moved to the settings file, no information should be written into the windows registry as that makes settings non-portable.

Describe alternatives you've considered

Additional context
image

@chummer5a

This comment has been minimized.

Copy link
Owner

commented Sep 12, 2019

No, pretty much every existing global option has a reason for being such. In the case of things that affect data files, that's because data files are global to the instance. I'm working on that in a separate branch.

@Nedorus

This comment has been minimized.

Copy link
Author

commented Sep 12, 2019

Pleased don't misunderstand my insistence as any form "non-appreciation" 😁 The contrary is the case. Your efforts for Chummer are always appreciated!

On topic: I'm not questioning the fact that things need to be global. But global could also be in a central config file, no?
In order to explain the need let me explain how I (and several of my players) use Chummer.
I have the entire Chummer directory in a Google Drive folder on a desktop PC. Any changes to any files (e.g. updates to nightly builds or configfile changes) are synched to G-Drive.
When I start my laptop then all files are synched from G-Drive to a local drive.
When I start Chummer on the laptop then I would like to not need to change additional stuff to make both installs work exactly the same.
Anything in the local registry needs to be changed locally. That is quite cumbersome.

So you see, that global should truly be global as in "across" all PCs not just on one PCs 😁

@chummer5a chummer5a added the feature label Sep 13, 2019
@ArchonMegalon

This comment has been minimized.

Copy link
Collaborator

commented Sep 16, 2019

That is something we want to get to anyway for better portability. I wonder, if the "store all the custom data for a group" should be the next thing i implement for sinners. Not sure, how often that would actually be needed, since the use case seems rather niche.

@Nedorus

This comment has been minimized.

Copy link
Author

commented Sep 16, 2019

Well improving portability would be the first step. And should be rather straight forward.

If we get the second step later on (group specific configs) that would be nice. But ... a second step 😂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.