20,741
edits
Canvas MapStructure: Difference between revisions
Jump to navigation
Jump to search
→Performance
| Line 284: | Line 284: | ||
[[File:MapStructure-ND-Profiling.png|thumb|MapStructure/NavDisplay testbed with integrated profiling support for each layer]] | [[File:MapStructure-ND-Profiling.png|thumb|MapStructure/NavDisplay testbed with integrated profiling support for each layer]] | ||
the performance issue related to the map-canvas.xml dialog pointed out by another user (whenooming) has nothing to do with Canvas or Nasal - it is C++ code that is causing this, and this is no surprise - it's a known issue actually. As a matter of fact, the hard-coded NavDisplay, as well as the hard-coded Map dialog both suffered from the exact same issue, until Gijs solved it by rewriting the projection handling code. | |||
However, the original Canvas projection code is still using the old implementation, i.e. the update got never back-ported: [[Canvas MapStructure#Performance]] | |||
We're talking here about roughly 50 lines of C++ code, which exist already and which would need to be turned into a Canvas::Map::Projection | |||
Note that this would benefit any, and all, Canvas-based NavDisplay/Map applications, too - also note that this information is readily available in various places, so there is no need to draw any wrong conclusions or spread any misinformation here.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=300979#p300979 | |||
|title = <nowiki> Re: Any plans for a new GUI? </nowiki> | |||
|author = <nowiki> Hooray </nowiki> | |||
|date = Dec 10th, 2016 | |||
|added = Dec 10th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
{{FGCquote | {{FGCquote | ||