-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deleting sketch caused Processing to delete my entire Downloads folder #424
Comments
Yikes, thanks for letting me know. I'll get a fix in ASAP. The problem is that the file wasn't in a sketch folder, so it seems to have assumed that the “Downloads” folder was the sketch folder. This is new as of beta 6, where we're trying to decouple the requirement for the sketch folder to be named the same thing as the That's tricky to sort out, but we'll think of something. And at a minimum we should only be moving files to the Trash/Recycle Bin so that if there's a glitch like this, it's recoverable. |
Fixed for beta 7, including:
Thanks for the report, and sorry for the trouble. |
This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs. |
Description
I downloaded a pde file from a friend and opened the pde file from the Downloads folder. Later, I tried to delete the sketch through the Processing app, and it ended up deleting everything in my Downloads folder, which was a lot of files. These files couldn't be found in the recycling bin either, so they were directly deleted by Processing.
Expected Behavior
I was expecting Processing to only delete my pde files.
Steps to Reproduce
Your Environment
Possible Causes / Solutions
Not sure, it seems like every time Processing deletes a sketch it deletes all the files in the working directory, but since I opened my pde file in the Downloads folder it made the Downloads folder the working directory and deleted everything in there.
The text was updated successfully, but these errors were encountered: