totalhouseof.blogg.se - Mouse is zooming instead of scrolling

The user should be able to choose to leave his choice always selected.

There should a visual indicator indicating in which mode is the scrolling being used: zoom, movement, nothing, etc.īy default it should be “nothing”. So how about different behaviour for viewing and editing? Does anybody see problems for other use cases?Įither option, by itself, lends to bad user experiences.Context is key.

Scrolling via mouse wheel allows to precisely scroll in one direction (exactly vertical or exactly horizontal).Ī problem of zooming via CTRL + mouse wheel is that it is caught by the Web browser if bpmn.io is embedded into a Web page.

Horizontal scrolling should also be usable from multi-touch touchpads and mice with horizontal mouse wheels, which make it more easy to use.

This could be an argument to treat pools, lanes and maybe even sub-processes differently for dragging. Same holds true when you want to use the lasso tool to select elements inside a pool but instead accidentally move a pool or lane. In this situation it is indeed annoying when dragging moves a pool or a lane.

In large collaborations the canvas is mostly hidden behind pools & lanes.

Dragging the canvas helps when it is visible.

More helpful would be automatic scrolling once the edge of the screen is reached.

If you runs out of space zooming doesn’t help. You mostly add shapes to a part of the model. During modelling you don’t change the abstraction level (zoom) all the time.

This style of scrolling is commonly known not only from Wen browsers, but also from desktop publishing and modelling tools that need to deal with large models while dragging is reserved for moving elements within these models.Google Maps style zooming and dragging is great for viewing large models.įor editing models though, I prefer Web style combined with a draggable canvas, because: