Develop

Ticket #1277 (closed enhancement: fixed)

Opened 2 years ago

Last modified 15 months ago

Custom flarm location

Reported by: scottp Owned by: hjr
Priority: low Milestone: XCSoar Manual
Component: User Interface Version: 6.3
Keywords: manual Cc:

Description

Add to interface appearance the ability to move the "FLARM radar" to another location. The info boxes and FLARM are more important than the map. Knowing bearing, distance to turn, current climb, average climb. So the FLARM radar could easily go over the map.

The new Interface Appearance moves the boxes, which would solve my problem, as the radar stays on the right, except that there is no other option (other than right) for Vario Needle.

Change History

comment:1 Changed 2 years ago by scottp

  • Owner set to scottp
  • Status changed from new to accepted

comment:2 Changed 2 years ago by scottp

Work in progress, added: Top Left, Bottom Left, Top Right, Bottom Right (default), Centre Top, Centre Bottom. Just need to review code style, constants, structure.

comment:3 Changed 2 years ago by scottp

There is now an "Auto" mode, which follows the location of the info boxes (within reason).

Long term this code may be one of Automatic move default then: Only in expert; or Only by hand in the profile file.

comment:4 Changed 2 years ago by scottp

Almost complete. Just needs code clean up. Tested PC, Altair, Android.

comment:5 Changed 2 years ago by Turbo

  • Priority changed from normal to low

comment:6 Changed 2 years ago by scottp

Complete, waiting review and pull

comment:7 follow-up: ↓ 8 Changed 2 years ago by apf

I strongly disagree with "The info boxes and FLARM are more important than the map". For me the map is the single most important element of xcsoar. It gives me the situational awareness I need like location of airspaces and reachable airfields with arrival height. Everything else is nice to have since the most important things are even available without xcsoar (glider instruments and FLARM display, albeit with less details). Obviously this depends on your flying region. If there are no airfields or airspaces within your glide range the map is less important but in the region I fly that would be highly unusual.

As long as the location of the "secondary" elements remains configurable I have no problem with this change.

comment:8 in reply to: ↑ 7 Changed 2 years ago by scottp

Replying to apf:

I strongly disagree with "The info boxes and FLARM are more important than the map".

Yes quite right. We discussed this in IRC and I neglected to update the ticket. Therefore the default is just to follow the info boxes. Thus the actual fix stops the flarm going over the map :-)

Thanks

Scott

comment:9 Changed 2 years ago by Turbo

  • Status changed from accepted to closed
  • Resolution set to fixed

comment:10 Changed 15 months ago by hjr

  • Keywords manual added
  • Status changed from closed to reopened
  • Version changed from 6.0 to 6.3
  • Resolution fixed deleted
  • Milestone changed from XCSoar 6.2 to XCSoar Manual

manual update needed

comment:11 Changed 15 months ago by hjr

  • Owner changed from scottp to hjr
  • Status changed from reopened to assigned

comment:12 Changed 15 months ago by hjr

  • Status changed from assigned to closed
  • Resolution set to fixed

done

Note: See TracTickets for help on using tickets.