Bug 403380

Summary:	Animation plays when Play is pressed in another opened file, even though Stop is pressed in current one
Product:	[Applications] krita	Reporter:	johannes.rave
Component:	Animation	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	ahab.greybeard, scottpetrovic
Priority:	NOR
Version First Reported In:	4.1.5
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description johannes.rave 2019-01-18 21:48:21 UTC

SUMMARY
When one of the opened files (in tabs) is playing animation, the other files will play their animated layers as well, even though the animation is "stopped" in their tabs. I had to stop animation in the file I had opened in the backround, to stop animation playing in my current working file.

STEPS TO REPRODUCE
1. Open more than one file with animated layers.
2. Play animation in one.
3. Switch to the other file.

OBSERVED RESULT
Animation is playing as well, even when "stop" is pressed in Animation docker.

EXPECTED RESULT
Animation playing on a per-file-basis


SOFTWARE/OS VERSIONS
Windows: 10.0.17134
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Ahab Greybeard 2019-01-19 10:48:47 UTC

I confirm that this happens in the Jan-18 build appimage (git 4f95062).

When one animation is Played, both start to play even though the other animation has the docker showing the Play icon (not the stop icon).

If you set both animations to 'playing' (i.e. with the Stop icon showing)  then both have to have their Stop icons pressed (to show the Play icon) before both will stop playing.

Comment 2 Scott Petrovic 2019-04-05 14:00:54 UTC

I just tested this on a nightly build (Krita 4.2) and I am pretty sure this is fixed now. I had two animation documents opened in separate tabs. I started playing one, switched to the other document tab, and the animation timeline stops playing.

This is what I would expect to happen. I am going to mark this as resolved for now. If the same issue is still there, you can re-open this one or make a new ticket if it is slightly different.