Bug 348288 - [ CTRL+click color-picker ] shortcut changed after update
Summary: [ CTRL+click color-picker ] shortcut changed after update
Status: RESOLVED DUPLICATE of bug 348234
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 2.9
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-27 06:37 UTC by David REVOY
Modified: 2015-05-27 07:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David REVOY 2015-05-27 06:37:05 UTC
Hi, 
After a fresh build from yesterday, the on-canvas CTRL+click color-picker had weird shortcut settings , making it unusable for a larger audience.

Bug
===
1. CTRL+left-click color-picker  => set to default : Pick background-color for current layer.
2. CTRL+alt+left-click color-picker  => set to a 'Tertiary' mode, making nothing, nothing display
3. CTRL+right-click color-picker  also mixed

How it should-be as default :
========================
1. CTRL+left-click color-picker  => set to default : Pick *foreground*-color for *merged* layer.
2. CTRL+alt+left-click color-picker  => set to default : Pick *foreground*-color for *current* layer.
3. CTRL+right-click color-picker  => set to default : Pick *background*-color for *merged* layer.
4. CTRL+alt+right-click color-picker  => set to default : Pick *background*-color for *current* layer.

I'll see if other default setting are also changed.
This type of change are easy to workaround for the one who knows how to go in the Krita configuration panel ; but I assume most audience will just believe it's new crappy and non-functional default.
Comment 1 Halla Rempt 2015-05-27 07:12:50 UTC
Yes, it's part of the fall-out from the second iteration of the selection modifier patch. We're tracking the issues here: 348234 so Michael can fix them coming weekend. I think we might have the full set now, so I can revert the patch again...

*** This bug has been marked as a duplicate of bug 348234 ***