Problem with renaming classes.

slo1958

I used find/replace to rename a few classes.

Wanted to rename the classes with a name starting with clLogingXXXX to clLoggingXXXX.

The classes were renamed as expected, but the IDE started to show the old name in the tree view and the new name in the property list on the left side.
Looking at the files (the project tis saved as version control), it seems the rename worked on the code part, but not on the json part.
You can find the source code on GitHub at slo1958/sl-oj-lib-logging

The 'main' branch is the source tree before the rename and the ‘renaming’ branch is the source tree after the rename.

problems-with-rename.pdf

165kB

Alternatively, I can provide the source tree as a zip, if easier.

See attached screenshot

Note the repo start with slo1958, no sl1958 as stated in the .pdf

Garry

Thanks for the report and the example project. Your diagnosis was correct: Find/Replace changed the class declarations and references without updating the saved item names. The Solution tree and Inspector were then reading different names, which also interfered with further renaming.

I’ve fixed this for the next release. Find/Replace now keeps the saved names, tree and Inspector consistent. The replacement also supports Undo and Redo as a single operation.

I’ve also added recovery for projects already affected. When you open your project in the next release, Studio will repair mismatched names where the declaration is unambiguous. It preserves your source code, folders and notes, and marks the repaired items as unsaved. Save the project to retain the corrections.

I’ve added regression tests covering the original problem, recovery, saving and reopening, further renaming, and undo/redo.

slo1958

Thanks again for fast resolution

Richard_And_Trisha

I am using 26.10.5 and still having problem to rename methods in windows and on modules.

I was just trying to rename the methods name from do_Save_UserDefault to do_Save_UserDefault_Preference and it keep changing back to the do_Save_UserDefault

Garry

The original Find/Replace problem with class names was fixed in 26.10.5, but I found additional issues while investigating your method-renaming report.

A checked rename could restore the old name without displaying why it had been rejected. Duplicated methods also weren’t receiving the same initial naming behaviour as newly added methods. I’ve implemented fixes for both for the next release.

I’ve posted the details and a workaround in your newer thread.