Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

8.2: unable to adjust crop?

Comments

15 comments

  • VirtualRain
    I had that issue yesterday as well. Submit a ticket with Tech Support.
    0
  • Permanently deleted user
    Exactly the same behaviour here. No cursor changing from + to the arrows in the edges of a selected crop. Clicking inside a cropped area (to move the selection) creates a new crop. Cropping is not usable that way.

    [quote="VirtualRain" wrote:
    I had that issue yesterday as well. Submit a ticket with Tech Support.


    VirtualRain, did Tech Support provide you with a solution yet? If yes, what was the outcome?

    Thanks !
    0
  • Robert Bijl
    I to have the same problem with 8.2.

    Did find the arrows. They are at about 1/4 inside the frame.

    Also curious about a solution.
    0
  • Andrei Kozlov
    Same here, filed support ticket, but they cannot reproduce the problem. Argh!
    0
  • Jim_DK
    I have reproduced the problem and we will get on it right away. Sorry for the inconvenience.
    0
  • Jim_DK
    The only realistic workaround to hunting for the handles is to hold shift and draw the crop again. This "shift" key allows you to draw a crop within a crop.
    0
  • Jim_DK
    This bug has now been localised to the "scaled desktop" settings for OSX. Running in native retina resoution all is ok, scaled shows the issue.
    0
  • Vonsbaek
    From my thread on 8.2 image viewer quality...

    Thanks for the reply.

    I found the bug i think. If I, in (system) display preferences set scaled display – more space, the images is pixelated. If left to default everything is good. Must be some dpi discrepancy between the system and capture one which was not present in 8.1?

    Regards.
    0
  • Permanently deleted user
    [quote="Jim_DK" wrote:
    This bug has now been localised to the "scaled desktop" settings for OSX. Running in native retina resoution all is ok, scaled shows the issue.


    Thanks Jim for your information. I have a Tech Support ticket opened for this issue and can reproduce it too. In OS X with display settings set to 'default for display' the crop tool works as designed. As soon as it ist scaled it doesn't.
    0
  • Jim_DK
    [quote="Vonsbaek" wrote:
    From my thread on 8.2 image viewer quality...

    Thanks for the reply.

    I found the bug i think. If I, in (system) display preferences set scaled display – more space, the images is pixelated. If left to default everything is good. Must be some dpi discrepancy between the system and capture one which was not present in 8.1?

    Regards.


    I'm away from my desk so can't check, but do we have a case on this?

    Please be sure to cross link posts with the URL if you feel it relevant.
    0
  • Vonsbaek
    I think it's relevant because the root of the problem must be the same. Sorry for hijacking the post 🤭




    [quote="Jim_DK" wrote:
    [quote="Vonsbaek" wrote:
    From my thread on 8.2 image viewer quality...

    Thanks for the reply.

    I found the bug i think. If I, in (system) display preferences set scaled display – more space, the images is pixelated. If left to default everything is good. Must be some dpi discrepancy between the system and capture one which was not present in 8.1?

    Regards.


    I'm away from my desk so can't check, but do we have a case on this?

    Please be sure to cross link posts with the URL if you feel it relevant.
    0
  • Ian Wilson
    Moderator
    Top Commenter
    I'd found the same crop issue on my MacBook Pro (Retina) which I was using with a scaled display. I can confirm that going back to the native resolution has resolved it.

    Ian
    0
  • NN635590479813149416UL
    Is there a fix coming for those of us who like to work in a scaled display setting as opposed to default?

    Thanks for helping me fix this problem in about ten minutes on this forum, huge help!
    0
  • Jim_DK
    There is, but a timeline is not something we can comment on.
    0
  • jkossen
    Just a post to confirm that 8.2.1 fixes this issue.
    0

Post is closed for comments.