Not really sure this is a bug or not, but its definitely inconvenient and think it might be a good idea to fix it in C2 to avoid problems for people using C2 programs.
When using NW.js to create folders will in some cases make it impossible to delete them again using standard windows operations. Which means that any normal user of window risk having serious problems getting rid of these folders again. Not even with a 3rd party deleting tools can you remove them.
The problem occurs as you create the folder and leave a blank space at the end of the folder name. "Test folder ", which will make the folder be created so it looks correct. However for some reason this cause serious problems for windows, which will make it not able to delete or rename it.
The only way to delete the folder, that I have find out, is to do it through the command prompt. Which is not something normal users of windows will be able to just figure out.
To delete the folder you have to write the following in the command prompt:
rd /s "\\?\C:\Users\Nimos\Test folder " <- (And remember the empty space after Test folder)
So would strongly suggest that NW.js automatically fix or give an error if an empty space is the last character in the folder name when creating one in C2.
Attach a Capx
Description of Capx
Just a button that create a folder in Users called Test folder
Steps to Reproduce Bug
1. Click the button to create the folder.
2. Browse to your users folder and try to delete it.
When trying to delete it. You will get an error saying that the folder doesn't exist in the current path anymore and therefore it cant be deleted.
That the folder was deleted.
Operating System and Service Pack
Construct 2 Version ID
212.2, but is related to NW.js and how folders are created.
Develop games in your browser. Powerful, performant & highly capable.
Closing as won't fix: this is just weirdness in the Windows shell. Similar problems can happen if you create a folder with a dot at the end of the name, which has affected the C2 editor itself in the past. It's not a C2 or NW bug, it's Windows! If we modify filenames before acting on them that probably just opens another can of worms, so I think we will leave it up to you to make sure all file and foldernames are valid, as all Windows developers have to.