20,741
edits
MapStructure Optimizations: Difference between revisions
Jump to navigation
Jump to search
m
→Allocating selectable ranges into groups
| Line 34: | Line 34: | ||
What this means is that we can be much smarter, and much more efficient, when updating the map - because we don't need to remove symbols, we may only need to "hide" them - because they may not be visible in the currently selected range, but they may be visible if one of the other selectable ranges is chosen. | What this means is that we can be much smarter, and much more efficient, when updating the map - because we don't need to remove symbols, we may only need to "hide" them - because they may not be visible in the currently selected range, but they may be visible if one of the other selectable ranges is chosen. | ||
The point being, we can stop removing symbols like | The point being, we can stop removing symbols like crazy when toggling between ranges and simply hide stuff that is outside our current visibility volume due to the currently chosen range and/or map mode. | ||
Thus, what we were originally talking about is treating each selectable range as a "'''visibility volume'''" that gets its own Canvas group: | Thus, what we were originally talking about is treating each selectable range as a "'''visibility volume'''" that gets its own Canvas group: | ||