# Welp... I guess I'm taking a walk now

**URL:** <https://discourse.processing.org/t/welp-i-guess-im-taking-a-walk-now/45251>\
**Category:** Community\
**Created:** [October 30, 2024, 9:34pm UTC](https://discourse.processing.org/t/welp-i-guess-im-taking-a-walk-now/45251 "2024-10-30T21:34:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![eightohnine](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/eightohnine/32/19793_2.png) [@eightohnine](https://discourse.processing.org/u/eightohnine)\
**Post date:** [October 30, 2024, 9:34pm UTC](https://discourse.processing.org/t/welp-i-guess-im-taking-a-walk-now/45251/1 "2024-10-30T21:34:30Z")

</div>

![autonamingLimit](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/0/4/040e19a6f7e8808c6ccc802e165c7f6cb389fe83.png)

---

<div class="post-metadata">

**Author:** ![eightohnine](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/eightohnine/32/19793_2.png) [@eightohnine](https://discourse.processing.org/u/eightohnine)\
**Post date:** [October 30, 2024, 9:36pm UTC](https://discourse.processing.org/t/welp-i-guess-im-taking-a-walk-now/45251/2 "2024-10-30T21:36:40Z")

</div>

“Computer says NO.”

 ![Screenshot 2024-10-30 at 22.35.17](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/4/8/485f592c608cf840feae7b5d4061c0194ea14f91.png)

---

<div class="post-metadata">

**Author:** ![quark](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/quark/32/26_2.png) [@quark](https://discourse.processing.org/u/quark)\
**Post date:** [October 30, 2024, 10:31pm UTC](https://discourse.processing.org/t/welp-i-guess-im-taking-a-walk-now/45251/3 "2024-10-30T22:31:23Z")

</div>

Never heard of that before 🤔

Found [this](https://github.com/benfry/processing4/issues/582)

---

<div class="post-metadata">

**Author:** ![eightohnine](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/eightohnine/32/19793_2.png) [@eightohnine](https://discourse.processing.org/u/eightohnine)\
**Post date:** [October 30, 2024, 11:14pm UTC](https://discourse.processing.org/t/welp-i-guess-im-taking-a-walk-now/45251/4 "2024-10-30T23:14:32Z")

</div>

I should have been more precise, this is only about sharing this easter egg and not about me having any issues with it.

Also, I just restarted Processing and then everything was fine.

I’m testing out ChatGPT Plus and putting its code writing through the wringer, rapidly copy/pasting generated code iterations into a new Processing sketch for quick evaluation and comparison to previous code. (If I find a solid or intriguing sketch foundation, I then switch to Sublime for the heavy lifting). I quickly burned through the auto-naming limit and bumped into that nerdy easter egg.

---

<div class="post-metadata">

**Author:** ![sableraph](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/sableraph/32/251_2.png) [@sableraph](https://discourse.processing.org/u/sableraph)\
**Post date:** [October 31, 2024, 1:15pm UTC](https://discourse.processing.org/t/welp-i-guess-im-taking-a-walk-now/45251/5 "2024-10-31T13:15:17Z")

</div>

For reference, this was discussed here:

> <https://github.com/benfry/processing4/issues/582>
>
> A student of mine struggeled with Processing 4 today, and ran into the following… behaviour. I was able to reproduce it:
> 
> \## Steps to Reproduce
> 
> \* start Processing, close it, re-start it again; repeat several times
>  
> or, 
> 
> \* start Processing, and create a number\[^1\] of new sketches 
> 
> \[^1\]: this number might be 26, as the last sketch I was able to create ended with \`z\`.
> 
> Then, at some point, the following dialog pops up:
> 
> !\[Time for a Break: You've reached the limit for auto naming of new sketches for the day. How about going for a walk instead?\](https://user-images.githubusercontent.com/922274/197599511-9bee2c5e-3408-4a49-ac07-38b4b3c6ba9a.png)
> 
> When trying to start Processing again, one gets this:
> 
> !\[Sunshine: No really, time for some fresh air for you.\](https://user-images.githubusercontent.com/922274/197598435-753d5f76-9ed0-42ae-a6a0-0f49d9f6be61.png)
> 
> That's it. One can \*\*no longer start\*\* Processing for an unknown period of time.
> 
> What is that, some kind of an Easter egg?! I find this rather inappropriate. Today, it only led to even more frustration for my students who are just starting to learn Python and Processing.
> 
> \## Expected Behavior
> 
> Please don't tell me Processing cannot "auto name" more than 26 sketches per day. Keep the funny messages, if you like, but allow Processing to start again. Thanks.
> 
> \## Environment
> 
> \* Processing version: 4.0.1
> \* Operating System and OS version: Windows 10

> Here’s how you may fix this on Windows 10:
> 
> 1. Go to C:\Users[User name]\AppData\Local\Temp\processing
> 2. Move the anonymous sketches (named like sketch\_000000a to sketch\_000000z) to another folder.
> 3. Start Processing again. It should open normally.
> 4. You may also manually create an empty .pde file outside of the Processing IDE and double click it.
> 
> The best way to avoid reaching the maximum auto-naming limit is to save your sketches.