Renaming project file may be useful for someone but it's something I personally don't find essential... It could be another PR if someone is interested to do it.

Agree that it would be better as a separate PR.

that are compatible with existing user's workflow and don't break anything for them

This PR changes the project creation workflow. Here's an approach that would minimize changes to the current workflow:

• Have a default project name, filename, and basepath already filled in. Something like "New Project", which is preselected so the user can change it if desired.
• For each of project name, filename, and basepath, if it is changed, change the other two options, provided the user has not yet changed the default.
• Extend the Preferences / General / Startup / Paths / Project files to accept . and .. to refer to the project base path and the project parent folder.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.