# On screen cursor

**URL:** <https://forum.defold.com/t/on-screen-cursor/66994>\
**Category:** Questions\
**Created:** [December 10, 2020, 10:17pm UTC](https://forum.defold.com/t/on-screen-cursor/66994 "2020-12-10T22:17:06Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![roccosaienz](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/roccosaienz/32/19991_2.png) [@roccosaienz](https://forum.defold.com/u/roccosaienz)\
**Post date:** [December 11, 2020, 10:48am UTC](https://forum.defold.com/t/on-screen-cursor/66994/7 "2020-12-11T10:48:38Z")

</div>

Many many thanks @britzl @Pkeod @dapetcu21.

About PC. In order to keep the aspect ratio above a minimum I have implemented letterboxing (top and bottom black rectangles to adjust for an aspect ratio less than (say) 1.2) (see here [Aspect ratio control - #13 by dapetcu21](https://forum.defold.com/t/aspect-ratio-control/66975/13)). The letterboxing uses a smaller viewport, hence I cannot draw a go-cursor. So, my question is: why implementing also a go-cursor (and the hardware-go switching) and not just continuously update the hardware cursor position (via defos) when there is a controller input?

---

_[View the full topic](https://forum.defold.com/t/on-screen-cursor/66994)._