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. ⚠️

Focus on wrong Photo while deleting

Comments

8 comments

  • Ian Wilson
    Moderator
    Top Commenter

    I'm not sure that you have misconfigured anything, and it can be disconcerting. I can't remember whether it has always done it like that, but I suspect not. Maybe put in a support case asking for it to be changed, or look to see whether there is one already and upvote it.

    https://captureone.ideas.aha.io/ 

    Ian

    1
  • MartinG

    Thank you very much, Ian. I asked a friend who is still working with version 16.3.x. He doesn't have the problem. So either it is a problem with a higher version than 16.3, or there is a corresponding configuration option. I'll keep digging. 

    0
  • Ian Wilson
    Moderator
    Top Commenter

    I'm pretty confident that there is no configuration option for this.

    Ian

    1
  • Thomas Kyhn
    Top Commenter

    I've noticed this too and also find it disconcerting that you appear to be about to delete another image than the one you intended to delete.

    0
  • Ian Wilson
    Moderator
    Top Commenter

    Thomas Kyhn - my perception is that something has changed here, and it didn't always behave like this, but I can't readily check it out on an older version. Is that your perception too?

    Ian

    1
  • Thomas Kyhn
    Top Commenter

    Ian Wilson – I'm not sure, but as I didn't notice it until some time within the last year, it's quite likely that it wasn't like this in earlier versions of Capture One.

    1
  • Jerry C

    I posted something that occurs in 16.3 similar to this in the past, but it might be related. After deleting a thumbnail (pressing the delete key on Mac), focus skips to the thumbnail after the next one. If two thumbnails are highlighted and deleted, the one after the next becomes the focus. Strangely, moving the images to a new folder or closing and reopening Capture One, restores normal behavior. This was acknowledged by support and it was suggested that I upgrade to 16.4 which support thought might correct the problem. 

     

    1
  • MartinG

    In the meantime, I have opened a bug report and posted a screen recording. I'm curious to see what the support team will find out.
    Thanks for your comments!

    0

Post is closed for comments.