Deleting photos works differently for two different catalogs
I'm running two different catalogs under Capture One 20 Win10. In one of them, if I select a photo and hit the Delete key, it moves the photo to the Catalog Trash. If I open the other catalog and select a photo and hit the Delete key, it deletes the photo right from my disk - bypassing the Catalog Trash.
I can't figure out why the same default key action does two different things depending on the catalog.
-
And you are sure that they are both catalogues, one is not a session?
0 -
Both are catalogues. I kept on trying to figure out why it was happening and thinking I hadn't noticed it working that way before, so I restored an earlier backed-up version of the catalogue so tested again and now deletes correctly (hitting Del key moves image to the catalogue trash). Anyway, only lost a few edits using the backup version and it seems OK now.
0 -
Brian,
It might be worth considering whether each catalogue was working with different settings for the Workspace and/or Keyboard Shortcut definitions.
When you close a catalogue (or session) the state as last used it also saved.
If you use a default and unchanged Workspace or KB Shortcut file it might be slightly differently defined after an update.
If you use your own definition in a personally named file it will not be changed but may work differently in the rare cases where some underlying definitions have been altered.
There is also the potential for the core Windows use of the Del key to delete stuff at the windows level.
C1's default KB shortcuts use modifier keys to request a full in system delete using the dedicated Windows Delete key but I am not totally convinced that Windows always responds as C1 software expects.
The situation seems to have been a bit fluid in recent year as C1 moved from having KB shortcuts but combined with some hard coded and dedicated keys that were "reserved" for specific purposes towards almost everything being open for re-definition in the Shortcuts.
If you happen to be using some legacy definitions then that could introduce scope for differences and some confusion.
0
Post is closed for comments.
Comments
3 comments