# Fullscreen/span

**URL:** <https://discourse.processing.org/t/fullscreen-span/8582>\
**Category:** Processing\
**Created:** [February 21, 2019, 12:35am UTC](https://discourse.processing.org/t/fullscreen-span/8582 "2019-02-21T00:35:17Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![kll](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/kll/32/964_2.png) [@kll](https://discourse.processing.org/u/kll)\
**Post date:** [February 21, 2019, 1:26am UTC](https://discourse.processing.org/t/fullscreen-span/8582/3 "2019-02-21T01:26:03Z")

</div>

how does that look?

```auto
void setup() {
  fullScreen();
  surface.setSize(200, 200); //Change size here
}

void draw() {
  background(0);
  ellipse(mouseX, mouseY, 20, 20);
}

```

more:

> [@Is setUndecorated() possible?](https://discourse.processing.org/t/is-setundecorated-possible/1097/10):
>
> No, I agree with you, and your first answer - overriding initSurface() - is the way I do this. Depending on the renderer and the OS, fullScreen() can set flags on the window that you don’t want and can cause problems. The slightly longer-winded way you posted first is a safer bet. I only use the OpenGL renderers in PraxisLIVE. Interesting these return the window and not the canvas from getNative() so I override initSurface like (where wHints is my own config object) - protected PSurface ini…

---

_[View the full topic](https://discourse.processing.org/t/fullscreen-span/8582)._