Opened 8 years ago

Last modified 7 years ago

#1239 new enhancement/feature request

External settings file

Reported by: bafplus Owned by: KaZeR
Priority: minor Milestone:
Component: core Version: git master
Severity: normal Keywords: settings
Cc:, (2)


Is it an idea to store all the settings variables in a file? Now we use navit.xml mostly for layout and design, but also for settings some variables. If we put those variables in a second file (settings.xml/txt) you can easaly save settings and. Now a lot of variables are from source.

Change History (3)

comment:1 Changed 8 years ago by tryagain

If you use gui_internal, navit reads commands from gui_internal.txt on start up. It even stores some settings made in internal gui, into that file.

Pleaase clarify your suggestion.

comment:2 Changed 8 years ago by bafplus

Only thing that is stored right now is the active layout. Would be nice to have more "options" that can be saved.

some sugestions:

  • Save current state at quit so Navit launches with same settings as last exit.
  • 2d/3d
  • Day/night
  • Zoomlevel
  • Active (map)layers
  • Define zoomlevels-speed for auto_zoom

I short: Use navit.xml for layout and core settings, use gui_internal for (more)"custom" settings.

comment:3 Changed 7 years ago by mvglasow (2)

  • Cc (2) added
Note: See TracTickets for help on using tickets.