Opened 13 years ago

Last modified 9 years ago

#447 new enhancement/feature request

Move OSD elements to the menu

Reported by: Owned by: cp15
Priority: major Milestone: version 0.6.0
Component: gui/internal Version: git master
Severity: Keywords:
Cc: sybren@…


It would be nice if users could configure certain "pages" in the menu to show OSD items. For example, my Magellan eXplorist 210 has a page based UI where the user can choose what to show in certain fields. The main page shows the map and two fields for things like ETA, speed, heading, etc. Other pages contain a compass and two more user-choosable fields, GPS coordinates, battery info etc.

By moving those fields away from the main "page", there is a very limited number of fields that need to be updated simultaneously and the screen remains uncluttered. By moving to another page the user can access more information, so there is a lot of info available but in such a way that the CPU load is still fairly low, and the screen fairly clean.

To me this sounds like a good design idea to apply to Navit. In short:

  • Pages with information, such as the map (main page), navigational info (ETA, next turn, etc.), compass.
  • OSD items can be placed on any page, not just the map.
  • Pages that are not displayed are also not updated.
  • Maybe the pages themselves should be configurable as well, but I'll be happy with a fixed set: map, navigation/routing, compass, system info (GPS coords, signal strength, GPS date/time, battery level)
  • Could be integrated into the menu, or the menu could be yet another page.

Change History (3)

comment:1 follow-up: Changed 13 years ago by kazer

  • Milestone set to want patch / contribution

Interesting idea. It could be done by loading OSD xml files on the fly.

comment:2 in reply to: ↑ 1 Changed 13 years ago by smt

Replying to kazer:

Interesting idea. It could be done by loading OSD xml files on the fly.

wich would be a great feature anyways

comment:3 Changed 9 years ago by usul

  • Milestone changed from want patch / contribution to version 0.6.0
Note: See TracTickets for help on using tickets.