Jump to content
walt.farrell

Crop dimensions change wildly

Recommended Posts

In 1.8.4.693, I've noticed the following behavior of the Crop Tool:

  1. Open an image.
  2. Switch to Crop Tool.
  3. Switch to Unconstrained mode.
  4. Note the dimensions. For my image, the crop size defaults to 1050px x 590px.
  5. I change the Units from Pixels to Inches, and I see this in the Context Toolbar:
    image.png.7fc3d643079d8c54a126ad33863ad925.png
     
  6. I now type "8in" into the width box, and I get this:
    image.png.7d88d6219c0babade50f65d8c41329c5.png
     
  7. If I again type "8in" into the width field, I get this (note that the width changed to the same wrong value, but the height jumped to a wildly different value):
    image.png.d2fa267e723f60f3cd9f6bce24b6b30f.png

-- Walt

Windows 10 Home, version 2004 (19041.388),
   Desktop: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970
   Laptop:  8GB memory, Intel Core i7-3625QM @ 2.30GHz, Intel HD Graphics 4000 or NVIDIA GeForce GT 630M
Affinity Photo 1.8.5.703 and 1.9.0.891 Beta   / Affinity Designer 1.8.5.703 and 1.9.0.891 Beta  / Affinity Publisher 1.8.5.703 and 1.9.0.887 Beta.

Share this post


Link to post
Share on other sites

More information:
The Context Toolbar has two fields for the crop size, an input field for width and height, and an output field showing the resultiing crop size.

I start with the Context Toolbar showing this when I invoke the Crop Tool:

image.png.dcce87b4c415fc3483ce5845d5ff165c.png

Both fields are consistent, and correct.

I change the units to inches, and I get this:
image.png.d74c8220da247436013c39129df3dbed.png

The input fields have been properly recalculated to be in inches. The output field has not changed. All is correct.

I then type a new width in the input field, and press Enter. If I use 8in I get this:
image.png.26246f61b10e83f3de1faee58534b7a9.png
 

Note that the input fields now say inches, but both are really in pixels and match the Crop field. The values are correct for pixels, given that DPI. It's only the units in the width/height that are shown incorrectly.

I then type 8in into the width field again, and get this:
image.png.3c36e45bc84f7188baed088b4cfb56e5.png

Note that the width remains the same incorrect 576 inches (is really 576 px). And the height has become 42525 inches. The Crop size shows 45256 px as the height.

Where did that height come from?

If I again type 8in into the width field and press enter I get:
image.png.d56d2954b4989c0418af2c0d0e5bf710.png

Again, notice the height value, which is now up to 3061800 inches. The units are wrong, but the value matches the shown crop height. But where did that height come from?

 


-- Walt

Windows 10 Home, version 2004 (19041.388),
   Desktop: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970
   Laptop:  8GB memory, Intel Core i7-3625QM @ 2.30GHz, Intel HD Graphics 4000 or NVIDIA GeForce GT 630M
Affinity Photo 1.8.5.703 and 1.9.0.891 Beta   / Affinity Designer 1.8.5.703 and 1.9.0.891 Beta  / Affinity Publisher 1.8.5.703 and 1.9.0.887 Beta.

Share this post


Link to post
Share on other sites
1 hour ago, walt.farrell said:

Where did that height come from?

590.625 × 72 = 42525

1 hour ago, walt.farrell said:

Again, notice the height value, which is now up to 3061800 inches.

42525 × 72 = 3061800


Alfred online2long.gif
Affinity Designer/Photo/Publisher for Windows • Windows 10 Home (4th gen Core i3 CPU)
Affinity Photo for iPad 1.8.6 • Designer for iPad 1.8.6 • iPadOS 14.3 (iPad Air 2)

Share this post


Link to post
Share on other sites

Thanks, Alfred. I hadn't gotten around to trying the calculations yet.


-- Walt

Windows 10 Home, version 2004 (19041.388),
   Desktop: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970
   Laptop:  8GB memory, Intel Core i7-3625QM @ 2.30GHz, Intel HD Graphics 4000 or NVIDIA GeForce GT 630M
Affinity Photo 1.8.5.703 and 1.9.0.891 Beta   / Affinity Designer 1.8.5.703 and 1.9.0.891 Beta  / Affinity Publisher 1.8.5.703 and 1.9.0.887 Beta.

Share this post


Link to post
Share on other sites
On 8/7/2020 at 3:05 PM, Chris J said:

Thanks Walt. It will be fixed ASAP.

Fixed in 1.8.5.703 Beta. Thanks!


-- Walt

Windows 10 Home, version 2004 (19041.388),
   Desktop: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970
   Laptop:  8GB memory, Intel Core i7-3625QM @ 2.30GHz, Intel HD Graphics 4000 or NVIDIA GeForce GT 630M
Affinity Photo 1.8.5.703 and 1.9.0.891 Beta   / Affinity Designer 1.8.5.703 and 1.9.0.891 Beta  / Affinity Publisher 1.8.5.703 and 1.9.0.887 Beta.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.