Bug 303025 - Refactoring after renaming class uses wrong class name
Summary: Refactoring after renaming class uses wrong class name
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (show other bugs)
Version: 4.3.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-04 17:27 UTC by Rolf Eike Beer
Modified: 2016-12-13 08:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.0.0
Sentry Crash Report:


Attachments
Renamed the class name for the first time which updated the constructor name (612.58 KB, image/png)
2016-04-21 00:11 UTC, Priyanka Bandaru
Details
Renamed the class name for the second time which updated the constructor name (614.12 KB, image/png)
2016-04-21 00:12 UTC, Priyanka Bandaru
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rolf Eike Beer 2012-07-04 17:27:38 UTC
Save this example as a header file:

#pragma once

class foo {
  foo() {}
};

Right-click on the class name and rename the class (e.g. to Foo). Now right click on the renamed constructor: it is shown as foo::Foo in the menu and if you e.g. select "create separate definition" then it will also be written as such.

If you instead just try to rename the class again the constructor will not get renamed again, but will keep the name after the first rename.

Reproducible: Always




I've tested this on 2 different hosts, one running SC 4.9rc1 on openSUSE 11.4, the other one running SC 4.8.4 on openSUSE 12.1, both using KDevelop 4.3.1.
Comment 1 Priyanka Bandaru 2016-04-21 00:11:22 UTC
Created attachment 98487 [details]
Renamed the class name for the first time which updated the constructor name
Comment 2 Priyanka Bandaru 2016-04-21 00:12:40 UTC
Created attachment 98488 [details]
Renamed the class name for the second time which updated the constructor name

I followed all the steps provided above and didnt find any issue.
Comment 3 Kevin Funk 2016-04-21 06:59:32 UTC
Confirmed. Assuming this got fixed in the meantime.