Bug 395866 - Animation Timeline & Transform Tool: Krita does two things at once (move layer, navigate on timeline)
Summary: Animation Timeline & Transform Tool: Krita does two things at once (move laye...
Status: CONFIRMED
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: 4.1.0 beta
Platform: Other Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-25 20:09 UTC by Tiar
Modified: 2022-12-29 23:14 UTC (History)
2 users (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 Tiar 2018-06-25 20:09:03 UTC
Krita cannot decide whether move the layer or navigate on timeline.

Steps to reproduce:

1) Create a layer.
2) Add a frame and paint on it (to see results later).
3) Use arrows to navigate on timeline: back and forth.
4) Click "T" and use arrows to move the picture left and right.

Actual results:

5a) Picture is moving AND the active frame is changing (previous/next and so on, according to the arrows)

Expected results:

5b) EITHER picture is moving (only transform tool is active) OR the active frame is changing (only navigating on timeline is active)

The preferred expected results: only transform tool is active; it is still possible to navigate on timeline after (somehow) going "out" of transform tool

Use-case:

1) Have a bunch of frames that need to be moved
2) Navigate through them with arrows
3) When on keyframe, click "T" and move the picture to correct location
4) Click "B" or something to end transforming, navigate on timeline (without needing to refocus on timeline) to the next (or other) frame
5) Repeat

(Needing to refocusing (with mouse) on timeline to navigate to the next interesting frame would be time-consuming and irritating)
Comment 1 Halla Rempt 2018-06-30 09:44:26 UTC
Jouni, 

Can you take alook?
Comment 2 joupent 2018-10-09 14:10:19 UTC
Looks like the frame switching actions are triggered through KisShortcutMatcher, while the move tool gets called directly from a QAction.