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

Undo/Redo should only work in the context of the currently selected image or variant

Comments

8 comments

  • Boris Tomsic

    It used to be more like what you're requesting but then after an update it changed, presumably in response to user feedback. But I'm with you and have added my vote

    0
  • Permanently deleted user

    Users requested that they wanted to be able to undo the selection of an image in the browser? It seems to make little sense, since selecting an image in the browser can hardly be seen as an adjustment, but it does congest the adjustment history. 

    I'm under the impression that not much time has been dedicated to such an important aspect of an image editing software.

    0
  • Class A

    This has been requested ("Image Edit History") over two years ago, has received considerable support, and has been forwarded to the developers (it was marked "Completed" and an internal request has been generated) .

    I would not harbour much hope, if I were you.

     

     

     

    2
  • Permanently deleted user

    @Class A

    I know that feature request, and I upvoted it. But instead of a (even more useful) non-sequentual undo option, like an adjustment history might provide, I am just asking to scope the undo/redo function to an image or variant.

    I have the suspicion that Capture One runs on a legacy code base that isn't very scaleable/manageable/modular, and therefore any change requires huge amounts of refactoring/rewriting. At least that would provide an explanation as to why even extremely popular feature requests like yours end up being ignored.

    0
  • Class A

    @Noob with a Nikon  

    Thanks for upvoting the other feature request.

    I agree that your request appears to be more modest but I believe in terms of implications, it is only a very small step from the functionality you are suggesting to the more comprehensive functionality I described.

    A major disincentive to implementing a permanent history -- your image-based undo history may only last as long C1 is running -- are the implications on the catalogue file size, plus someone would have to define the database schema for histories.

    I think the main problem with C1, from my personal perspective, is that Capture One's goals are not aligned with people who use a lot of layers / editing operations per image and care about productivity. Capture One, the company, seems to overlook the weaknesses of C1 in that area and instead focuses on features that promise to widen the user base (-> HDR, panorama, tablet support, make C1 very beginner-friendly (sometimes at the cost of more experienced users)).

    1
  • Kevin Robbins

    I hope if this were implemented, it would be done as an option to toggle. I prefer the current way, especially when editing a large number of images. There is real need and use for deselecting multiple images.

    0
  • Permanently deleted user

    I hope if this were implemented, it would be done as an option to toggle. I prefer the current way, especially when editing a large number of images. There is real need and use for deselecting multiple images.

    Aren't those 2 different things? Undo/Redo should be for image adjustments. Then, if there's a need to deselecting multiple images, C1 should provide an option for that.

    0
  • Class A

    @Kevin,

    the feature request is not mutually incompatible with the global undo functionality as is currently implemented.

    One would just have two different "undos" (say in the form of two different keyboard shortcuts).

    In other words, if the feature were implemented, it would be super easy to still offer the current behaviour that you prefer.

    1

Post is closed for comments.