# Using surface.setLocation does not do same thing every time

**URL:** <https://discourse.processing.org/t/using-surface-setlocation-does-not-do-same-thing-every-time/11871>\
**Category:** Coding Questions\
**Created:** [June 5, 2019, 7:01pm UTC](https://discourse.processing.org/t/using-surface-setlocation-does-not-do-same-thing-every-time/11871 "2019-06-05T19:01:14Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![glv](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/glv/32/18785_2.png) [@glv](https://discourse.processing.org/u/glv)\
**Post date:** [April 14, 2026, 7:23pm UTC](https://discourse.processing.org/t/using-surface-setlocation-does-not-do-same-thing-every-time/11871/12 "2026-04-14T19:23:36Z")

</div>

> [@quark](#):
>
> I suspect it is either something to do with Windows 10 or how Processing interacts with Windows 10

I did some further exploration here: [Native window access and inset handling in Processing JAVA2D and P2D](https://discourse.processing.org/t/native-window-access-and-inset-handling-in-processing-java2d-and-p2d/48437)

`:)`

---

_[View the full topic](https://discourse.processing.org/t/using-surface-setlocation-does-not-do-same-thing-every-time/11871)._