-
Notifications
You must be signed in to change notification settings - Fork 7
Modify highlighting #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| showSearchResults(featureIds) | ||
| //=========================== | ||
| { | ||
| this.unselectFeatures(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, this used to be the behaviour and then a decision was made (a FCCB request??) to never zoom in to just the found features (and always zoom out so all found features are visible). Has this decision been reversed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cannot find noZoomIn is used anywhere. Instead, the default zoomIn is set to false in the zoomToFeatures(). I assume the parameter noZoomIn was updated to zoomIn sometime in the past.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct!
| animate: false | ||
| }) | ||
| return bbox | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
|
PR closed as the changes are not ideal. A new issue has been created. |
The changes here are for the ticket - Improve Flatmap highlight/selection speed
options.sequenceis added to make sure the selected features will remain.bboxis returned and passed in to make sure the bounds will always fit.Currently, there is a short time delay when highlighting a large number of features. Allowing highlighting neuron paths by chunk should be able to minimize the time delay from paths selected to paths highlighted. Although the total time cost may remain the same.