Feature thoughts

[BridgeAR]

This issue is meant to memorize feature requests that are not yet fully explained. I'll close this after opening dedicated issues for each of these entries:

• Feature: Re-add an indicator / button to unfocus. This was recently changed but it's not completely intuitive right now.
• Feature: Add a "Export" feature. This allows to save a screenshot for each custom configuration. Each file is saved one after the other. Needs further details and better custom configs.
• Follow-up feature (screenshot follow-up): Check for the most outer bounds of all custom configurations. Those bounds may now be used for the screenshot export and make sure that all custom configurations always have the same viewpoint. If the angle of the custom configurations are identical or converge by up to 10% use an angle that is the median of those angles. Otherwise, show a list of angles that the user wants to use for the exported screenshots. The user may now chose if the export uses these bounds or the actual custom configuration bounds and angles.
• Increase default margin between folders and buildings to the current 100%
• Increase margin range that a user might chose from. The value should not be a relative one anymore as there's no corresponding value to compare the percentage to. Instead, use pixels that are scaled. The range could be e.g., 1 - 100 pixels.
• Scale labels depending on the zoom factor
• Fix labels clipping into buildings
• Make sure the folder size is calculated precisely instead of using an estimate
• Add individual metrics. These may be defined by the user by passing through a JS function

---

• ~~Feature: Highlight the chosen file when right clicking on a file in the search (e.g., different color)~~ #1068
• ~~Bug: delta mode broken when comparing with identical file after original open (open two files, switch to delta, compare identical file)~~ #1067
• Adjust this issue: Hiding options should be adjustable with an option
• ~~Feature: Provide tooltip / description for each metric - both primary and secondary. These descriptions have to be added to the cc.json file from the importer. The fields are optional to stay backwards compatible~~ #1066
• ~~Feature: Custom scenario indicators and remove button are indistinguishable. Add some space in-between or add a line~~ #1069
• ~~Feature: Keep the viewpoint angle intact. Right now during e.g., focus / unfocus the map always changes the angle to the default values instead of keeping the users former angle~~ #1070
• ~~Feature: A right mouse button click on a map node should provide a new option called "Keep highlighted" (naming TBD). This should keep the currently visible parts identical to the way they are visible right now even when moving the cursor away.~~ #1323
• ~~Feature: Save current configuration. Add a button to the main menu (next to "scenario") that allows to save the current setting. It requires a setting name. As soon as saved the setting (redux state without the cc.json part - the latter is ) (simple + or "add" button next to an input field for the name) it's possible to jump back to that configuration / setting by clicking on the configurations name. Next to the configuration name there's a delete button (similar to the custom scenario ones). This is only kept in memory! Do not use the local storage.~~ #1318
• ~~Feature: Completely rewrite the download part. Instead of creating a new cc.json file we'll save the current redux state in a file. This file is named myFile.config.json and it includes a hash value that corresponds to the actual myFile.cc.json. It is now possible to load this configuration in combination with the original cc.json file and sets the state accordingly. If the hash does not match the cc.json file, an error is visualized that the config does not match the cc.json. This could be implemented with a feature flag, since it's not sufficient to replace the old download immediately.~~ #1472
• ~~Follow-up feature: Download configurations. It's possible to download all custom configurations in a batch download. Each cc.json file gets a unique configuration file. In case delta / or multi is used the configuration may only be used for this specific setup. The loading button should now allow to load the configuration at the same time as the cc.json file. TBD if loading the config.json without a corresponding cc.json should error or if it should handle the use case gracefully. Gracefully means it's possible to load the configuration up-front and then load the cc.json afterwards. The user is then able to choose the config in the menu.~~ #1472
• ~~Show folder names as part of the folder. Mainly for big folders or only for the top n levels?~~ #1491
• ~~Allow to change the displayed colors (red, yellow, green, grey) to something arbitrary~~ #1556