Load settings from main window.
See original GitHub issueQuality-of-life improvement: Allow loading settings file from main window context menu.
Example: context->load->Sorceress Hell
where Sorceress Hell
is the file Sorceress Hell.conf
.
The idea is to allow quickly switching configuration when switching characters or run type without having to go through the route of opening up the settings window, locating the save file, etc…
Required features:
- Keep track of all save files saved/opened with the program (history).
- Show available settings-files in context menu.
- Allow deleting settings-file history from the context-menu.
- Allow loading settings-file from the context-menu.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Save and load settings in a UWP app
Load a setting by first getting an ApplicationDataContainer instance for the local settings data store with Windows.Storage.ApplicationData.
Read more >How to: Read application settings - .NET Framework
This article shows you how to add a simple setting to an App.config file in a .NET Framework app, and then read the...
Read more >WPF mainwindow content load from a page
The way I have done this is to have a Frame in the XAML like so: <Frame Grid.RowSpan="4" Grid.ColumnSpan="3" x:Name="_NavigationFrame" ...
Read more >How to Store and Retrieve Setting In WPF - YouTube
This video demonstrates how to implement an Application preference feature that allows a user to read and modify application settings and ...
Read more >Windows Forms - Creating and Loading Main ...
The MainForm Load event handler: Instantiating and setting the application settings when the main application window is displayed for the first ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have forked the code and implemented a quick, basic version of this.
I am in two minds as to whether it is actually necessary to track history in any complicated way. If you are going for one file per config approach I think it is easier to just provide the context menu with config files found under an application/settings directory. It saves all the hassle of tracking stuff saved to multiple locations.
For a simple application like this, I would lean towards having one config file that contained multiple settings groups rather than multiple files.
Some nice changes to the UI for managing the configs could also make it much easier to work with multiple files.
@feyd @qhris or maybe as a different idea, have the DI data reading stuff as a library and bots/other tools can use that lib? what do u think about that?
and for contact, nice and oldschool, here is an irc: https://webchat.quakenet.org/ /join diablointerface