Ronald Niederhagen

Good point, we might add `IsOpenVario()` to Asset.hpp and evaluate for `HasTouchScreen()` .

Part of the problem: the map moves while the pilot is trying to move the cursor to the object and anticipate the right moment for hitting the button. A hit_radius...

I'm using the 7" Texim display. According to the datasheet it has 133.3 dpi in X and Y. I have not yet seen a method to read this directly from...

> This can backfire pretty badly if you have a jiggly input device (say, trackball). You might never see a map moving that way. Good point. I didn't think of...

I checked yesterday and in my opinion it's not solved. It still uses `HasTouchScreen()` to determine the hit radius. But not every device with the need for a wider hit...

Did you try to start xcsoar with explicit DPI argument? `xcsoar -dpi=168x177` Does it still produce the exception?

Understand. So I guess https://github.com/skylines-project/skylines/issues/2154 is a mute point.

Here is an other issue: Airspace structures change over time. For instance airspace C around Munich has changed significantly as of March 2020. Or ED-R138A replaced ED-R138 a couple of...

I'll put it on my ToDo list for after the season. @Turbo87 , can you elaborate what you do when you "manually import into the database".

Your device may think you have a pointing device like a mouse. Instead it should think it has a touch screen. This widens the click radius. You try this by...