From fb4f6051cfbc32b871eef96c2823963ca489470f Mon Sep 17 00:00:00 2001 From: Gus Grubba Date: Thu, 1 Feb 2018 00:01:14 -0500 Subject: [PATCH] Updating readme --- src/Airmap/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/Airmap/README.md b/src/Airmap/README.md index c57893947..b8a0c0dd4 100644 --- a/src/Airmap/README.md +++ b/src/Airmap/README.md @@ -4,7 +4,7 @@ * Group rules jurisdictions -* Check rules sorting order. Repopulating QmlObjectListModel causes the repeater to show the contents in random order. +* ~Check rules sorting order. Repopulating QmlObjectListModel causes the repeater to show the contents in random order.~ * ~AirMapRestrictionManager seems to be incomplete (if not redundant). Shouldn't we use the array of AirSpace items returned by AirMapAdvisoryManager instead? In addition to the AirSpace object, it gives you a color to use in order of importance.~ See question below. @@ -20,4 +20,4 @@ Given a same set of coordinates, what is the relationship between the `Airspace` Also, the main glaring airspace nearby, KRDU has one entry in Airspaces whose ID is not in the array returned by the advisories (and therefore no color to assign to it). In fact, KRDU shows up 20 times in Advisories and 11 times in Airspaces. -In summary, why do I have to make two requests to get two arrays of Airspaces, which should be mostly the same? \ No newline at end of file +In summary, why do I have to make two requests to get two arrays of Airspaces, which should be mostly the same? -- 2.22.0