-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Fix move and rotation map tools preview when layer crs != canvas crs #51445
Conversation
Isn't it expensive to do a feature request and iteration on each update? If it's negligible or there's no way around, fine. Otherwise I would assume that creating a single entity and just moving it around would be more efficient, instead of refetching the data and transforming it? |
You're probably right. I had no visible performance issue with my data, but they were extrememely simple polygons. I'll update the PR when I have the time. |
mRubberBand->updatePosition(); | ||
mRubberBand->update(); |
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.
why are these 2 lines dropped?
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.
If I'm not mistaken, setTranslationOffset
already updates the rubberband, making the call to updatePosition
and update
redundant.
bf396b5
to
da9df38
Compare
Description
Fixes the Rotate Feature and Move Feature maptools previews, when the layer crs is not the same as the map canvas destination crs.
Current behavior
Fixed behavior