MapStructure Optimizations: Difference between revisions

Jump to navigation Jump to search
Line 68: Line 68:


=== Clipping invisible searchCmd results ===
=== Clipping invisible searchCmd results ===
Since property I/O is known to be the major culprit when it comes to Canvas performance, it makes sense to optimize anything that can help reduce the amount of property accesses (reads/writes).
SearchCmd() as such is just a function that returns a vector of search results, for each vector element, the layer-specific symbol controller will be invokved to instantiate/animate and update the corresponding element.


Since we're -so far- only doing range-based filtering, this means we're also adding elements, and thus properties, that may not even be visible - e.g. due to the currently selected map mode and/or the FOV.


Thus, it would make sense to do additional clipping/filtering at the searchCmd() level by allowing constraints to be specified to exclude/filter entries that are not visible.


== Related ==
== Related ==
{{Appendix}}
{{Appendix}}

Navigation menu