Document Setup

[Eddy-2]

Designer 1.10.5.1342, Windows 10.

Not a major problem.

I create a new document, 110mm w x 210mm h, portrait with 10mm margins.

I click on Document Setup and change the width to 90mm, then OK.

The margins readjust as expected but the overall width remains at 110mm.

Zooming in or out clears the problem and resets the dimensions.

[NathanC]

Hi @Eddy-2,

Are you referring to the overall width of the document remaining at 110mm until zooming in/out? I was not able to replicate this issue, as when I resized the document to 90mm w the canvas immediately resized along with the margins re-adjusted to 10mm.

Does the issue still occur after disabling Hardware Acceleration in Preferences > Performance? If so, could you perhaps provide a recording demonstrating this? Thanks!

[joe_l]

26 minutes ago, NathanC said:

If so, could you perhaps provide a recording demonstrating this?

Same for me. HWA is off. Recording attached.

[NathanC]

7 minutes ago, joe_l said:

Same for me. HWA is off. Recording attached.

Thanks for demonstrating, still working as expected on my setup. Do you mind sending over a screenshot of your performance preferences?

[joe_l]

3 minutes ago, NathanC said:

Do you mind sending over a screenshot of your performance preferences?

 

[NathanC]

Thanks, This still may be a rendering issue, if you set the renderer to the software (WARP) does it still occur after restarting?

[joe_l]

1 minute ago, NathanC said:

if you set the renderer to the software (WARP) does it still occur after restarting?

Still happens.

[Eddy-2]

Hello Nathan.

The three attachments, new document, change width and zoom out detail the problem.

After disabling Hardware acceleration, the problem persists.

Something I've just noticed is that when I increase the width back from 90mm to 110mm, the document resizes as expected.

Also attached is the document preferences after disabling Hardware Acceleration.

[Eddy-2]

Thanks Hens.

I've changed the UI to dark (and Renderer to WARP) and it still happens.

[NathanC]

Thanks for the details, I can confirm we've been able replicate this issue and it has now been logged with the developers for resolution. 🙂

[Eddy-2]

Thanks Nathan.