Eoin Flood created NETBEANS-4575:
------------------------------------
Summary: Renaming an unsaved file causes incorrect warning and
destroys edits
Key: NETBEANS-4575
URL: https://issues.apache.org/jira/browse/NETBEANS-4575
Project: NetBeans
Issue Type: Bug
Components: cnd - Editor
Affects Versions: 12.0
Environment: Windows 10
Reporter: Eoin Flood
Steps to reproduce:
# Create or open a file in a project
# Make some edits in the file
# 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
# This appears to be bugged behaviour, as 2 warnings should not appear at
once, one above the other.
# This can destroy work done, as the renamed file will now only contain the
content since last edited or created
# 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
