Bug 356058

Summary:	Krita Animation Beta - Frame Ranges Cannot Be Selected With Graphic Tablet Stylus
Product:	[Applications] krita	Reporter:	sayantan.chaudhuri+kde
Component:	Animation	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bhupen.aole, griffinvalley, halla
Priority:	NOR
Version First Reported In:	2.9.10
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description sayantan.chaudhuri+kde 2015-11-29 09:01:53 UTC

Ranges of frames cannot be selected on the Animation Docker by shift+clicking. And yet, the mouse can be used to perform the same action, and the stylus can be used to select individual frames, as well as arbitrary sets of frames with ctrl+click.

Reproducible: Always

Steps to Reproduce:
1. Create some frames.
2. Select any frame.
3. With the stylus, click on a distant frame.

Actual Results:  
Firstly, the some white frames of the same amount as the ones between the selection and the shift+click destination immediately flash to the right of the destination click, but then disappear.

No frames are actually selected. But the original selection is deselected and the destination is selected instead.

Expected Results:  
The original selected frame, all frames going up to the destination frame, as well as itself, should be selected. No such flash should occur.

My graphic tablet is a Wacom Bamboo One CTE-660. It functions as expected everywhere else in the system, as well as throughout the rest of Krita, with the Wacom Linux drivers.

This strange flashing issue is hard to screencast as it shows up for a single screen-draw frame, (probably.) 

After failing to select the frames with the stylus, if I try to shift+click with the mouse a range is selected from the original frame, despite the Docker showing that the destination frame from the stylus-triggered action being selected and highlighted.

Comment 1 sayantan.chaudhuri+kde 2015-11-29 09:07:36 UTC

EDIT: Instead of "Animation Docker" I meant "Timeline Docker". I apologize for the error.

Comment 2 Bhupen 2015-12-03 14:33:05 UTC

There seems to be a way to select keys with stylus, using the small grey boxes above the blue keys in the timeline. Click on one of the boxes then drag it to inc. the selection.

But shift+click would be nice to have too specially in cases where the number of keys are not contained in the timeline box.

Comment 3 wolthera 2015-12-03 17:03:43 UTC

I cannot confirm this in 3.0 on Kubuntu 15.10 with the intuous 3.

Maybe we can pinpoint if it only happens with certain resolutions?

Comment 4 sayantan.chaudhuri+kde 2015-12-07 14:32:15 UTC

Additional information: I can select arbitrary frames with ctrl+click just fine with the tablet.

I have been unable to arrange to test the animation beta on a different system with Windows with my own tablet as well as my friend's tablet (which, unfortunately, is also a Wacom Bamboo.) I plan to do this and report as soon as possible.

(In reply to Bhupen from comment #2)
> There seems to be a way to select keys with stylus...

Does this mean you can reproduce the bug's behavior on your system Bhupen?

Additionally, I just tested the trick to select frames with those tiny flat darker squares, and it worked! But only a few times! Now it's not selecting again, but no weird flashes like the shift-select behavior, this now just selects whatever frame I end on!

(In reply to wolthera from comment #3)
> ...Maybe we can pinpoint if it only happens with certain resolutions?

My system's resolution is 1600x900 pixels. The tablet is mapped to the full resolution.

I also just tested to see if this behavior changed with differently sized Krita windows. The behavior persists still :[

Comment 5 sayantan.chaudhuri+kde 2015-12-12 04:28:31 UTC

The reported behavior still remains on the reported system on the animation beta version 2.9.10

Comment 6 Halla Rempt 2016-03-31 18:59:31 UTC

But also with 3.0?

Comment 7 sayantan.chaudhuri+kde 2016-04-01 05:22:29 UTC

I just tested with the 3.0 Alpha AppImage [ krita3-prealpha3-de0d43d-x86_64.appimage ] and this behavior is no longer present. 

Frame-range selection with a stylus now works as expected.