# Move/rotate draw order

**URL:** <https://discourse.shapr3d.com/t/move-rotate-draw-order/44>\
**Category:** Modeling Questions\
**Created:** [January 30, 2016, 6:26am UTC](https://discourse.shapr3d.com/t/move-rotate-draw-order/44 "2016-01-30T06:26:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shawnkirsch](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/shawnkirsch/32/19_2.png) [@Shawnkirsch](https://discourse.shapr3d.com/u/Shawnkirsch)\
**Post date:** [January 30, 2016, 6:26am UTC](https://discourse.shapr3d.com/t/move-rotate-draw-order/44/1 "2016-01-30T06:26:30Z")

</div>

Looks like the draw order for the move/rotate tool is not drawing in 3D. I have a tough time selecting the right manipulator sometimes.

See image (red move tool and blue rotate tool are cruelly reversed in distance to camera)

![](https://cdck-file-uploads-us1.s3.dualstack.us-west-2.amazonaws.com/flex002/uploads/shapr3d/original/1X/266c55a8744103dea8f3f637739fe4652735e035.png)

---

<div class="post-metadata">

**Author:** ![Istvan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/istvan/32/23668_2.png) [@Istvan](https://discourse.shapr3d.com/u/Istvan)\
**Post date:** [January 30, 2016, 9:32am UTC](https://discourse.shapr3d.com/t/move-rotate-draw-order/44/2 "2016-01-30T09:32:06Z")

</div>

Yes, very awkward… Since the handles have to be on the top, the depth test is disabled when we are rendering them, so we would have to order them manually, but we didn’t do that yet. Will be done in the next release.

---

<div class="post-metadata">

**Author:** ![Tamas\_Shapr3D](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/tamas_shapr3d/32/41_2.png) [@Tamas\_Shapr3D](https://discourse.shapr3d.com/u/Tamas_Shapr3D)\
**Post date:** [February 1, 2016, 1:54pm UTC](https://discourse.shapr3d.com/t/move-rotate-draw-order/44/3 "2016-02-01T13:54:58Z")

</div>

Thanks for your bug report Shawn! This was annoying indeed 🙂 Just writing to let you know that this bug has already been fixed so it’s definitely coming in this Friday’s release.