[NETBEANS-4575] Renaming an unsaved file causes incorrect warning and destroys edits

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 12.0
• Fix Version/s: 12.2
• Component/s: cnd - Editor

Environment

Windows 10

• Assignee: Unassigned
• Reporter: Eoin Flood
• Created: 12/Jul/20 09:44
• Updated: 03/Jan/21 13:12
• Resolved: 03/Jan/21 13:12

Description

Steps to reproduce:

1. Create or open a file in a project
2. Make some edits in the file
3. Rename the file in the Projects window

Result:

2 warnings will appear. The first will say "This object cannot be renamed from  [name] to [new name]" . The second will open, obscuring the first, and will say "File [name] was changed to read-only! All changes will be discarded". The first warning turns out to be incorrect, as the file will be renamed as required, but any edits made will be lost. This also highlights a problem with the second warning - there is no option to tell the program to keep the edits or to cancel the rename.

Issues

1. This appears to be bugged behaviour, as 2 warnings should not appear at once, one above the other.
2. This can destroy work done, as the renamed file will now only contain the content since last edited or created
3. This is not how Netbeans behaved in previous versions. Previously renaming files worked perfectly regardless of whether any edits were made.

Comments:

The functionality of previous versions of Netbeans was very valuable and is highly desirable. Being able to rename a file without concern. If that cannot be re-instated, some way to keep the work done seems required.