# Editing window Cursor out of register Windows 10

**URL:** <https://discourse.processing.org/t/editing-window-cursor-out-of-register-windows-10/34622>\
**Category:** Processing\
**Created:** [January 14, 2022, 10:53am UTC](https://discourse.processing.org/t/editing-window-cursor-out-of-register-windows-10/34622 "2022-01-14T10:53:35Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Simon\_Schofield](https://avatars.discourse-cdn.com/v4/letter/s/3ec8ea/32.png) [@Simon\_Schofield](https://discourse.processing.org/u/Simon_Schofield)\
**Post date:** [January 14, 2022, 10:53am UTC](https://discourse.processing.org/t/editing-window-cursor-out-of-register-windows-10/34622/1 "2022-01-14T10:53:35Z")

</div>

> please format code with \</\> button \* [homework policy](https://discourse.processing.org/faq/#homework) \* [asking questions](https://discourse.processing.org/t/2147)  
> Not sure if this is the right place to report this. But for me it’s an app-killer problem for Processing 4 on Windows 10, and am surprised more haven’t flagged it up.

The insertion point of the text cursor in the code-editing window is off. So the cursor shows blinking at a particular point on a line, but if you insert of delete text this happen a number of chars to the left of the blinking cursor. It gets worse with long lines of text, so is OK on the very left hand side or a line, but is about 10 chars out on a long line.  
A student of mine has just tried it on his laptop and has the same problem. It make the system unusable. Tried changing font to monospace, automatic scaling etc in preferences but the problem persists.

---

<div class="post-metadata">

**Author:** ![paulgoux](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@paulgoux](https://discourse.processing.org/u/paulgoux)\
**Post date:** [January 16, 2022, 6:25am UTC](https://discourse.processing.org/t/editing-window-cursor-out-of-register-windows-10/34622/2 "2022-01-16T06:25:56Z")

</div>

More info please, what version of p5 are you using, new install?

---

<div class="post-metadata">

**Author:** ![Simon\_Schofield](https://avatars.discourse-cdn.com/v4/letter/s/3ec8ea/32.png) [@Simon\_Schofield](https://discourse.processing.org/u/Simon_Schofield)\
**Post date:** [January 18, 2022, 9:56am UTC](https://discourse.processing.org/t/editing-window-cursor-out-of-register-windows-10/34622/3 "2022-01-18T09:56:19Z")

</div>

Hi Paul

It’s the Java-based processing desktop app for PC. Processing 4.0b2-windows 64. Running on Windows 10.

best wishes

Simon

---

<div class="post-metadata">

**Author:** ![paulgoux](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@paulgoux](https://discourse.processing.org/u/paulgoux)\
**Post date:** [January 20, 2022, 1:02pm UTC](https://discourse.processing.org/t/editing-window-cursor-out-of-register-windows-10/34622/4 "2022-01-20T13:02:51Z")

</div>

Have you checked processing github to see if there are similar issues.

Do previous versions produce the same error and have you tried a clean install.

All else fails i would try an alternative ide. I know its not the ideal solution…

---

<div class="post-metadata">

**Author:** ![hotfooted](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/hotfooted/32/3670_2.png) [@hotfooted](https://discourse.processing.org/u/hotfooted)\
**Post date:** [January 23, 2022, 12:35pm UTC](https://discourse.processing.org/t/editing-window-cursor-out-of-register-windows-10/34622/5 "2022-01-23T12:35:05Z")

</div>

it’s to do with windows scaling. you can read more [here](https://github.com/processing/processing4/issues/226)

---

<div class="post-metadata">

**Author:** ![Simon\_Schofield](https://avatars.discourse-cdn.com/v4/letter/s/3ec8ea/32.png) [@Simon\_Schofield](https://discourse.processing.org/u/Simon_Schofield)\
**Post date:** [January 25, 2022, 1:28pm UTC](https://discourse.processing.org/t/editing-window-cursor-out-of-register-windows-10/34622/6 "2022-01-25T13:28:28Z")

</div>

Yes, changing Display Settings → Scale and Layout to 100% (was 150% recommended) fixed it. Thanks Hotfooted. But now all my apps have reallllly small UI elements. Not what I would have chosen, so this is a work-around in my book. Think it still needs a fix in the short term.