No display of file name... Really?

0 favourites
  • 8 posts
From the Asset Store
Source File, music and art pack for Android Negotiator
  • As much as I love Construct and consider it to be a triumph of usability and UI design, I find it shocking and bewildering that the actual file name of the project you are working on is not shown to the user anywhere, unless I am missing something. The only place it seems to appear is when you have multiple projects open, that have no project name, then it is appended.

    As a UI connoisseur I have to say this is a failure of the most fundamental sort.

    In general the approach to project naming is a mess. There should be two additional options in the settings. (1) Show file name. One obvious place would be at the very top of the Project Bar above the Project Name, and, more importantly (2) Use file name as project name.

    Having the Project Name be different than the File Name is useless to begin with in my opinion, and only invites confusion. I have 325 Construct projects, alot of it just experimentation and learning, but so be it. The only option to have cohesiveness between the file names and project names is to manually evaluate all 325 projects, and then manually rename all of the files and projects, and then any time a change is made to one or the other, it has to be tracked and then accounted for. This is a terrible UX and workflow/productivity design IMO.

  • I understand you are talking about c3p files, and I agree sometimes I need to see the file name, usually when I have two versions of the same project open.

    However, in C3 you can also save projects as a folder or to a cloud service. Displaying a file name in these cases will be useless.

  • I understand you are talking about c3p files, and I agree sometimes I need to see the file name, usually when I have two versions of the same project open.

    However, in C3 you can also save projects as a folder or to a cloud service. Displaying a file name in these cases will be useless.

    No, no cloud, only local. It's a nightmare trying to manage a large number of files. A huge amount of unecessary time and effort for something that should be simple. Not just not being able to see the file name, but the fact that the project name is a separate entity unconnected to the file name drives me crazy. This is a terrible way to work, and I can't think of any other software of the caliber of Construct that forces users to work this way.

  • You need to post a suggestion and hope it gets enough votes..

    construct3-21h2.ideas.aha.io

  • I think it makes sense to keep the project name separate. Some people will want to set them separately. For example you might have "My game (variant 1).c3p" and "My game (variant 2).c3p" for testing or experimentation purposes, and you want both to have the project name "My game". If the filename automatically sets the project name, it makes it impossible to do that - the file system will prevent you having two projects with the same name, because you can't have two files with the same name.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • I think it makes sense to keep the project name separate. Some people will want to set them separately. For example you might have "My game (variant 1).c3p" and "My game (variant 2).c3p" for testing or experimentation purposes, and you want both to have the project name "My game". If the filename automatically sets the project name, it makes it impossible to do that - the file system will prevent you having two projects with the same name, because you can't have two files with the same name.

    Thanks for the personal reply Ashley, I really appreciate it coming from the founder, and it's nice to meet you. I think the negatives considerably outweigh the positives. It makes file management very difficult. I can't think of other sophisticated software (which Construct certainly is) that operates this way. It should be an option in any case. Let the user decide if they would like to work in a more traditional fashion. Any time we make creative projects, be it in Premiere or InDesign or Reason, the file name is the project. It's natural and normal and efficient and logical.

    I have hundreds of js files that I create and manage in VS Code, all declarations for content for educational games. I can't imagine if each of them had a separate name for the "project" and the "file," and then I also couldn't see the file name anywhere. It would be a nightmare to manage, and it's what I've come up against in C3.

    In the example you give they both have the same MyGame name in the filename anyway, followed by a version number. I don't think many people will call their game "Jungle Adventure v1.c3p" and then make version 2 and not call it "Jungle Adventure v2.c3p".

    If possible, please consider including the display of the filename somewhere if nothing else. It makes it very hard to manage large numbers of files. It's always best for users to have direct control over and awareness of their files. If the filename were visible then the issue of whether to derive the project name from the filename would be a moot point really. Users who prefer to focus on the file name would just do that and ignore the project name. The project name has no relevance when managing the actual files on disk though, which is what makes file management so difficult. You have to syncronize everything, and track changes, and then you can't even see the filename when you're working in the editor.

    Please don't get me wrong, I absolutely love Construct. It's genius, and hats off to you personally, just IMO this is a thorn in an otherwise brilliant product, and I haven't encountered many other thorns, which is saying a lot for such a robust product.

  • I ran into this as well and searched everywhere (kinda figured it might be on one of the statistics pages) and never found it. Finally had to just get used to trusting that I had the right file open and am now very careful when opening projects.

  • The project filename is already displayed in the Project Bar if you open two projects with the same name. So I'm not sure where any ambiguity would come from. Either you have one project open and presumably you know which you opened; or you have two projects open with different names so you can tell them apart; or you have two projects open with the same names but then Construct adds the filenames in the project bar so you can tell them apart.

    It makes sense to show the filename in the editor in a few more places anyway just to make things clearer, so I've added it to the tab tooltips and also as a tooltip to the project name in the project bar.

    As for the project name vs. filename, the project name is used in all sorts of places for things like the app name or the document title for web exports. Quite apart from the problem of "what's the filename of a project you haven't saved yet?", I'm sure not everyone will want that to match the filename - for example whether you use "My game (variant 1).c3p" or "My game v1.5.c3p", you may well want the app name/document title to just be "My game", i.e. different to the filename. If we made it use the filename, I can imagine someone writing an equally impassioned plea that we add a separate project name so they can control it separately to the filename. Not everyone uses software the same way, and we have to design Construct to work for a wide range of customers and usage styles. It's probably easy to critique software design and say it should work exactly how you want it, but it's not always the case that all the thousands of people who use Construct all want that as well. As with most things, there are subtleties and trade-offs to consider.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)