Request a new feature, or support for a camera/lens that you would like to use in Capture One.
When loading a previously customized and saved workspace, it would be nice to mark it as the currently active one. A checkmark alongside the menu entry would suffice to provide the functionality.
With the current behaviour, it's sometimes hard to tell which workspace is loaded (and which to overwrite with any changes made). This is especially worthwhile when starting out to customize C1 to your personal needs and can cause quite some confussion, at least for me ;-)
C1 should find them if the user appdata has been copied over (assuming the user name is the same.)
Retaining last editing status informations may be a little trickier if disks or computers are replaced without a very recent backup. But that is usually quite transient information anyway and so offers only minor, short-term inconvenience if any.
As a sole user of my PC, I keep access to the appdata folder open.
I could see that people with usage patterns different to mine might prefer a more managed option for creating and saving/restoring much of the data that ends up in appdata.
Hello! I’ll give you an example, in some cases when you save something like a preset, brushes, keybinds, it’s all saved into the appdata/roaming folder, which MS doesn’t want anyone to mess with as it’s hidden by default (same in MacOS).
I do backup all these files in my cloud just to be sure if my PC dies or I buy a new one I can recover all my settings back to the program, and work like nothing happened, but C1 or even PS doesn’t have anywhere to load them unlesss you go back to the hidden folder and reload the program, using like a profile for all of those or letting us load it from the UI would be less intrusive to system folders, hope I explained myself as english is not my primary language.
Just a little bump on usability for us freaks with many presets. 🤓
It would be good if there was some possibility to indicate that the current workspace is current entirely as created or has some changes (i.e. unsaved and possibly temporary) revisions.
Omar,
It will always be necessary to allow C1 to load new default and included Workspaces.
If one modifies a default workspace the best option is to save it with your own naming convention. Something that would never be delivered in a future update of Workspaces by C1 development.
However, that also means that we users must take responsibility for adding new tools and features to our workspaces when we decide we would like to use them.
I'm not quite sure what you have in mind when you mention a context menu. It does sound interesting.
I would also ask, if we can avoid the Workspace reset with every new update/release, because it messes up things sometimes.
Also the ability to save and load it from a context menu instead of fussing around hidden folders to save the preset "just in case".
+1, thanks
Yes, that would be great.
^^ spam ^^
+1