You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current organisation of settings (in the asr file) and profile items (in the json file) seems to follow no clear philosophy. I suggest to differentiate between settings the user might want to change or adapt during a session according to his needs and the profile, which should contain data for the display which should not be required by the user to be changed. So the more static data will be in the json, and any user customisation in the asr file. Or in other word, anything you can change as a user should be in the asr, what you can't change directly remains in the json.
I therefore suggest the following changes regarding the json file:
remove entry "cursor": use the default one when no value is found in the asr file, save the value to the asr
change font size to a value that can be entered by the user and save this value in the asr, remove the preset for the 5 sizes in the menu and the json
move "pro_mode" to asr, the "accept_pilot_squawk" might be considered taken from the ES settings
move "auto_deconfliction" to asr
move "leader_line_length" to asr
move "extended_lines_length" to asr
move "extended_lines_ticks_spacing" to asr
The text was updated successfully, but these errors were encountered:
The current organisation of settings (in the asr file) and profile items (in the json file) seems to follow no clear philosophy. I suggest to differentiate between settings the user might want to change or adapt during a session according to his needs and the profile, which should contain data for the display which should not be required by the user to be changed. So the more static data will be in the json, and any user customisation in the asr file. Or in other word, anything you can change as a user should be in the asr, what you can't change directly remains in the json.
I therefore suggest the following changes regarding the json file:
The text was updated successfully, but these errors were encountered: