# Shift for isometric line – strange behaviour
**URL:** https://community.aseprite.org/t/shift-for-isometric-line-strange-behaviour/3095
**Category:** Bug Reports
**Created:** [May 17, 2019, 7:44pm UTC](https://community.aseprite.org/t/shift-for-isometric-line-strange-behaviour/3095 "2019-05-17T19:44:25Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Glitcher](https://community.aseprite.org/u/Glitcher)
#### Post date: [May 17, 2019, 7:44pm UTC](https://community.aseprite.org/t/shift-for-isometric-line-strange-behaviour/3095/1 "2019-05-17T19:44:26Z")
I’m not sure if this is a bug or a feature, bug when I hold Shift to produce isometric lines (2x1), as I’m drawing it, every other pixel gets added the beginning of the line instead of its end.
As this is pretty difficult to explain, here’s a gif:
I’m sure this didn’t happen in previous versions, the odd pixel always just got added to the end of the line – where the cursor is. If this is new behaviour, please add an option to use the old one instead, I don’t like my lines not being actually isometric in 50% of the cases.
Thank you.
---
### Author:  [@dacap](https://community.aseprite.org/u/dacap)
#### Post date: [May 17, 2019, 10:37pm UTC](https://community.aseprite.org/t/shift-for-isometric-line-strange-behaviour/3095/2 "2019-05-17T22:37:03Z")
Yes, it’s a regression. (Actually old versions of Aseprite worked in this way, then it was fixed, and now is broken again 😭 we’ll release a fix next week)
---
### Author:  [@dacap](https://community.aseprite.org/u/dacap)
#### Post date: [June 10, 2019, 10:40pm UTC](https://community.aseprite.org/t/shift-for-isometric-line-strange-behaviour/3095/3 "2019-06-10T22:40:41Z")
This should be fixed in [v1.2.12](https://community.aseprite.org/t/aseprite-v1-2-12/3257) released today.
---
### Author:  [@dacap](https://community.aseprite.org/u/dacap)
#### Post date: [June 10, 2019, 10:40pm UTC](https://community.aseprite.org/t/shift-for-isometric-line-strange-behaviour/3095/4 "2019-06-10T22:40:47Z")