| Summary: | Need more smoothed solution when failed exporting unsupported color space | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Tyson Tan <tysontanx> |
| Component: | Usability | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | halla |
| Priority: | NOR | ||
| Version First Reported In: | 2.9 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | All | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Tyson Tan
2015-03-04 01:50:16 UTC
I'm pretty sure this is a duplicate of another bug, but I cannot find it... I'm not sure about not warning the user, though -- that's likely to lead to people getting really confused about losing their precision or color information. (In reply to Boudewijn Rempt from comment #1) > I'm pretty sure this is a duplicate of another bug, but I cannot find it... > I'm not sure about not warning the user, though -- that's likely to lead to > people getting really confused about losing their precision or color > information. Yes, I agree with you. I do think letting the user to control color conversion is very important. However, showing error messages that terrifies new user and completely blocks save/export function without any instruction is confusing. I suggest we show a YES/NO dialogue like this: " The {target file format} your are saving does not support the {incompatible colorspace} / {incompatible channel} by its specification. It will be automatically converted into {fallback colorspace} (Note: You can convert manually in Menu>>Image>>Convert Colorspace. Do you want to continue? [Yes] [No] " *** This bug has been marked as a duplicate of bug 342141 *** |