You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NovelWriter (justly) rejects the creation of a new project it its location already contains an existing projects.
However, this rejection comes after completing the wizard.
This means the user was permitted to fill in project details even though these will be lost due to the rejection.
Rejection should happen as soon as the document location is known.
Steps to reproduce the behaviour
Create a project in a new location
Close the project
Create a new project at the same location
On completion of the wizard, creation is denied because of the location.
What I expected to happen
On the second wizard screen, once a location is entered, progress to the next wizard screen should be possible only if location is valid (nonexistent or existent but empty); if progress is not possible, then the reason should be stated below the field for entering the location.
error dialog shown at end of wizard:
A project already exists in that location. Please choose another folder.
The text was updated successfully, but these errors were encountered:
vkbo
changed the title
When creating a project with the same location as an existing one, location is rejected late
A new project in a location with an existing project fails after the wizard
May 11, 2022
For both creations I chose the same project name and I selected the same "base" folder: /home/$USER/Writings, so for both projects the resulting location was the same /home/$USER/Writings/ProjectName.
Yes, that's an unusual case. TBH, I was trying out the predefined and custom layouts, and I wondered whether/how creating an existing project was handled (rejected? Renamed? Other?) so I actively chose the same project in the same folder each time. :)
I can add a check and warning for the case when the folder already exists and isn't empty. It would prevent people from having to go through the Wizard twice to correct the problem.
Description
Steps to reproduce the behaviour
What I expected to happen
error dialog shown at end of wizard:
The text was updated successfully, but these errors were encountered: