Is your feature request related to a problem? Please describe.
Currently the only way to use view feature is to replace tile paths in config.toml for demo view. That is not convenient.
Describe the solution you'd like
The implementation consists of 2 parts - main functionality and UI. The main functionality should be mostly there, we need to save chosen view and allow it works with more entries other than demo view.
Main Functionality
We need to be able to add more entries to the config.toml with other views (except for tirol_demo_view). Those will have the same structure as the demo view, but we will have to add a couple of parameters to both to allow adjustment for different computers, like loaded area radius for example to be able to save some memory.
The implementation should be relatively straightforward, we take the other parameters (not demo view but the other view) and pass them to run the renderer to .from_launcher(). Current architecture should allow that even though some small tweaks migh be necessary.
UI
In select DEM screen we need to have a third option - custom view. When clicked 2 more frames should appear, on the right, close to the menu frame there should be a narrow column-like frame with the current views and a button to create new (delete/edit existing views), the second one is a big frame appear in the moddle of the screen right after the column with saved views. It should also be semi-translicent. It should look like a table with 3 columns: base tire tiles, close tier tiles and fine tier tiles. we should be able to add many files to those columns (just with a system file picker for now).
This table (in the big frame) should also be split in 2 horisontally, upper part is for picking tile files, bottom part is for tier settings. Tier settings are loaded_part_radius and reload_radius, maybe something else but not sure yet. the view is saved in the config.toml file with a unique given name with uderscores instead of spaces e.g. My View -> my_view.
Describe alternatives you've considered
An alternative is to just modify demo view in the config.toml. Adding new entries to the config toml will still require code changes to make it work.
Additional context
The primary goal is to implement the fuctionality working with toml file, the UI is secondary.
Is your feature request related to a problem? Please describe.
Currently the only way to use view feature is to replace tile paths in config.toml for demo view. That is not convenient.
Describe the solution you'd like
The implementation consists of 2 parts - main functionality and UI. The main functionality should be mostly there, we need to save chosen view and allow it works with more entries other than demo view.
Main Functionality
We need to be able to add more entries to the config.toml with other views (except for tirol_demo_view). Those will have the same structure as the demo view, but we will have to add a couple of parameters to both to allow adjustment for different computers, like loaded area radius for example to be able to save some memory.
The implementation should be relatively straightforward, we take the other parameters (not demo view but the other view) and pass them to run the renderer to .from_launcher(). Current architecture should allow that even though some small tweaks migh be necessary.
UI
In select DEM screen we need to have a third option - custom view. When clicked 2 more frames should appear, on the right, close to the menu frame there should be a narrow column-like frame with the current views and a button to create new (delete/edit existing views), the second one is a big frame appear in the moddle of the screen right after the column with saved views. It should also be semi-translicent. It should look like a table with 3 columns: base tire tiles, close tier tiles and fine tier tiles. we should be able to add many files to those columns (just with a system file picker for now).
This table (in the big frame) should also be split in 2 horisontally, upper part is for picking tile files, bottom part is for tier settings. Tier settings are loaded_part_radius and reload_radius, maybe something else but not sure yet. the view is saved in the config.toml file with a unique given name with uderscores instead of spaces e.g. My View -> my_view.
Describe alternatives you've considered
An alternative is to just modify demo view in the config.toml. Adding new entries to the config toml will still require code changes to make it work.
Additional context
The primary goal is to implement the fuctionality working with toml file, the UI is secondary.