[Digikam-devel] [Bug 125735] New: Can't disable individual Monitor/Workspace/Input/Proof profiles

[fj.cruz at supercable.es]

---- Duncan Hill <kdebugs at nacnud.force9.co.uk> escribió: 
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>          
> http://bugs.kde.org/show_bug.cgi?id=125735         
>            Summary: Can't disable individual Monitor/Workspace/Input/Proof
>                     profiles
>            Product: digikam
>            Version: unspecified
>           Platform: unspecified
>         OS/Version: Linux
>             Status: UNCONFIRMED
>           Severity: wishlist
>           Priority: NOR
>          Component: general
>         AssignedTo: digikam-devel kde org
>         ReportedBy: kdebugs nacnud force9 co uk
> 
> 
> Version:           0.9 SVN (using KDE KDE 3.5.2)
> Compiler:          gcc 4.0.2 prerelease 
> OS:                Linux
> 
> In .9 SVN, digiKam assumes that if there is a file that matches the category, then the file should be loaded.  The only way to disable any of the profiles is to move it out of the directory, and reset the configuration options.  It would be nice if the dropdowns offered 'None' as an option for each profile category, allowing the user to selectively disable categories if they want to.
> _______________________________________________
I think a "None" option makes no sense, let's me explain this:

For a basic color management system you need at least two profiles: an input and an output/workspace one, if you select "none" for one of them, then you are breaking the color workflow, this is, you are disabling the CMS.

On the other hand, the monitor profile works only if "Managed view" option is enabled and the proof profile is usefull if you use the CM plugin avaliable in Image Editor and showfoto.

Paco Cruz