Skip to content
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

Print - Selected scale must not be auto. adapted #3649

Merged
merged 1 commit into from
Mar 12, 2018

Conversation

ger-benjamin
Copy link
Member

Fix: GEO-1051

Summary:
If the scale 1:1000 is never the "best calculated scale" for the print, the scale will be automatically adapted. Than means, we will never be able print in 1:1000. This PR correct that.

@jwkaltz can you test if that's the expected behaviors ? I've taken the same client-scale/print-scale than your, as explained in your comment, in the ticket.
@fredj can you valid the code ?

Demo here: https://gmf-test.sig.cloud.camptocamp.net/bge

@ger-benjamin ger-benjamin added this to the 2.2 milestone Mar 12, 2018
@ger-benjamin ger-benjamin self-assigned this Mar 12, 2018
@ger-benjamin ger-benjamin force-pushed the selected_scale_must_not_change branch from f8553ee to 484e609 Compare March 12, 2018 14:22
Copy link
Member

@fredj fredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ger-benjamin
Copy link
Member Author

@jwkaltz Tested by @eleu . I merge

@ger-benjamin ger-benjamin merged commit 5ad6ec9 into 2.2 Mar 12, 2018
@ger-benjamin ger-benjamin deleted the selected_scale_must_not_change branch March 12, 2018 15:46
@jwkaltz
Copy link
Member

jwkaltz commented Mar 12, 2018

@ger-benjamin I have updated https://gmf-test.sig.cloud.camptocamp.net/wkaltz22 and the test case I had works now (1:1000), thanks.

@ger-benjamin
Copy link
Member Author

ger-benjamin commented Mar 13, 2018

Also close: #3458

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants