Hard to scroll toolbox by dragging on touchscreen

[drigz]

An extremely bad gif of the current behaviour.

If you try to scroll the toolbox by clicking/touching a block and dragging horizontally, it will pluck the block out of the toolbox. This means you have to either use the scrollbar or the margins around the blocks, both of which are hard to hit on a touchscreen.

Based on dragAngleRange_, it seems Blockly has support for scrolling in this case. Any idea why isn't not working for Scratch-Blockly?

It also seems that Blockly only enables it for non-closable flyouts (presumably, when categories are disabled), which seems unhelpful. Any idea why that is?

[tmickel]

dragAngleRange was something we just added into Scratch-Blockly - it doesn't exist in Blockly. It's currently only applied for fixed (non-categories) toolboxes as you said, because this is the case we needed it for, and it wasn't clear to me what the behavior should be in closeable flyouts. In general I think we won't be using the closeable flyouts. If you need this please feel free to add it.

[drigz]

Sorry for the false report, I was using an old version of Scratch-Blockly when I tested the non-closeable flyout. We'll be using a non-closeable flyout as well, so I'm happy with that - thanks very much for adding the feature already!

One question: is there a reason you use angle rather than vertical offset? I find that if I follow a path like this with my scroll drag, I accidentally pull the block out of the toolbox - presumably because as I pass under the point of initial mousedown, the angle appears vertical, despite the general horizontal intent.

[tmickel]

Ok good!

That is a good question. I think using vertical offset is worth playing with, and I'll make a new issue for it.

@carljbowman

[rachel-fenichel]

It's using the combination of angle and offset (DRAG_RADIUS, I think).
Possibly the radius needs to be larger, at least while it's in the flyout?

On Tue, Apr 12, 2016 at 8:20 AM Tim Mickel notifications@github.com wrote:

Ok good!

That is a good question. I think using vertical offset is worth playing
with, and I'll make a new issue for it.

@carljbowman https://github.com/carljbowman

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#205 (comment)