Improve highlighting performance in zoomToFeatures().

[ddjnw1yu]

Although I understand how this can be used, I wonder about the rationale behind it, and the need for the caller to incrementally expand the selected features by passing in a bounding box, presumably returned from the previous call to zoomToFeatures().

If you are looking to improve performance by not unselecting and then reselecting previously selected features, then what about a new option called say selection, with values of clear (the default), expand (the current selected feature set is enlarged), and contract (the current selected feature set is shrunk)? Then the external client doesn't have to concern itself with internal representation.

Please raise an issue if you agree that this is better approach that will meet your needs -- it's straightforward for me to implement.

Originally posted by @dbrnz in #50 (comment)

[ddjnw1yu]

Wondering if there are any updates on this implementation?

[dbrnz]

@ddjnw1yu thanks for the follow up! It was put on the back-burner due to FC maps and APS -- now back on to it and will aim to have something ready next week.

[alan-wu]

@ddjnw1yu thanks for the follow up! It was put on the back-burner due to FC maps and APS -- now back on to it and will aim to have something ready next week.

Thanks a lot, here is the wrike ticket tracking on this work, I have now included you as one of the assignees.

https://www.wrike.com/open.htm?id=1589847586