[Request] Splitting Options config file #243

New Issue

Closed

opened 2026-01-29 16:12:41 +00:00 by claunia · 1 comment

claunia commented 2026-01-29 16:12:41 +00:00

Owner

Copy Link

Originally created by @Madroms on GitHub (Oct 11, 2020).

Originally assigned to: @mnadareski on GitHub.

As DICUI.exe.Config is part of the distribution files, your own options saved are replaced with the defaults one when you update your DICUI install.
2 config files will be better:

• a default one
• a user specific one

Or no config file available with the distribution of DICUI, the config file could be generated with the first use of the program. And when the program is updated, the new version checked if an old config file exists and updates it with newly added options (so you may add the DICUI version that generated the config file, as a parameter written inside it.

Originally created by @Madroms on GitHub (Oct 11, 2020). Originally assigned to: @mnadareski on GitHub. As DICUI.exe.Config is part of the distribution files, your own options saved are replaced with the defaults one when you update your DICUI install. 2 config files will be better: - a default one - a user specific one Or no config file available with the distribution of DICUI, the config file could be generated with the first use of the program. And when the program is updated, the new version checked if an old config file exists and updates it with newly added options (so you may add the DICUI version that generated the config file, as a parameter written inside it.

claunia added the enhancement label 2026-01-29 16:12:41 +00:00

claunia closed this issue 2026-01-29 16:12:41 +00:00

claunia commented 2026-01-29 16:12:42 +00:00

Author

Owner

Copy Link

@mnadareski commented on GitHub (Oct 12, 2020):

I know what you're asking for, even if you didn't ask it in the way I expected. The actual fix for this is to stop including the config file by default and have it generate so it doesn't overwrite for cough careless users on upgrade.

@mnadareski commented on GitHub (Oct 12, 2020): I know what you're asking for, even if you didn't ask it in the way I expected. The actual fix for this is to stop including the config file by default and have it generate so it doesn't overwrite for *cough* careless users on upgrade.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

rolling

3.6.0

3.5.0

3.4.2

3.4.1

3.4.0

3.3.3

3.3.2

3.3.1

3.3.0

3.2.4

3.2.3

3.2.2

3.2.1

3.2.0

3.1.9

3.1.8

3.1.7

3.1.6

3.1.5

3.1.4

3.1.3

3.1.2

check-rolling

ui-rolling

3.1.1

3.1.0

3.0.3

3.0.2

3.0.1

3.0.0

2.7.5

2.7.4

2.7.3

2.7.2

2.7.1

2.7.0

2.6.6

2.6.5

2.6.4

2.6.3

2.6.2

2.6.1

2.6

2.5

2.4

2.3

2.2

2.1

2.0

1.18

1.17.1

1.17

1.16.1

1.16

1.15

1.14

1.13

1.12.2

1.12.1

1.12

1.11

1.10

1.07

1.06

1.05.1

1.05

1.04b

1.04a

1.04

1.03

1.02b

1.02

1.01d

1.01c

1.01b

Labels

Clear labels

bug

duplicate

enhancement

good first issue

help wanted

invalid

pull-request

Mirrored from GitHub Pull Request

question

regression

wontfix

No Label enhancement

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

claunia

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/MPF#243