C2 renames files to lowercase on export

Problem Description

Construct 2 renames all project files to lowercase on export. Referring to them by name (not by Request project file), such as when loading web fonts therefore doesn't work.

Attach a Capx

http://www.filedropper.com/exportrenamelowercase

Description of Capx

Loads a .css project file by name, the file uses uppercase letters. It works as intended during preview, but breaks after export, because the code is still referring to it as "MySuperStylesheet.css" while it was renamed to "mysuperstylesheet.css" during export.

Note: some servers may be configured to be case-insensitive. However, Android Cordova build is not one of them.

Steps to Reproduce Bug

• Open the .capx attached.
• Run a preview. Observe the style of the button.
• Export the project.
• Run the exported project. Observe missing style of the button.

Observed Result

Construct 2 renames the project file to lowercase on export. Therefore, the requested file is not found. The style falls back to no special styling.

Expected Result

Construct 2 should not rename files on export OR should rename them on import and notify the user about the change.

Affected Browsers

• Editor problem.

Operating System and Service Pack

Windows 10, Windows 7

Construct 2 Version ID

r253, r244

I searched 'Closed Bugs' and found this post from Ashley:

[quote:3kim9uiw]

...all references are in lowercase to work on case sensitive servers.

I reckon this is probably still the case, so not a bug, really.

I searched 'Closed Bugs' and found this post from Ashley:

[quote:3lxk6xm1]

...all references are in lowercase to work on case sensitive servers.

I reckon this is probably still the case, so not a bug, really.

I think that C2 should notify the user on import that it will be renamed (and rename it instantly), otherwise the user may wonder why something doesn't work when exported, but it did work before exporting.

If you take a look at the exported "data.js" file, you'll still find the uppercase reference (in this case "MySuperStylesheet.css"), the way it was written in the events.

Closing as this is by design.

It's hard to know even when to notify users. We've had other kinds of warning notifications in the past and ended up removing them, because experienced users got tired of them.