Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Plugins development => Topic started by: gtafan on October 11, 2018, 01:45:53 pm

Title: Syncronization between h/hpp and c/cpp files
Post by: gtafan on October 11, 2018, 01:45:53 pm
Posibly this feature already exists in codeblocks, but I haven´t found it yet. So what I´d like to have is when I create a void in the h/hpp file the feature should create an empty implementation in the corresponding c/cpp file. Also when changing something on the void in the h/hpp the changes could be also done in c/cpp if the user wants it so.
Title: Re: Syncronization between h/hpp and c/cpp files
Post by: stahta01 on October 11, 2018, 06:16:57 pm
Posibly this feature already exists in codeblocks, but I haven´t found it yet. So what I´d like to have is when I create a void in the h/hpp file the feature should create an empty implementation in the corresponding c/cpp file. Also when changing something on the void in the h/hpp the changes should be also done in c/cpp.

I never noticed this feature; but, I do not use CB as a editor very much.

I would like the first part of creating an empty implementation; but, I would not like the second part.

Tim S.
 
Title: Re: Syncronization between h/hpp and c/cpp files
Post by: Quiss on October 12, 2018, 06:28:15 am
Right click c/cpp file, Insert/Refactor->All class methods without implementation.
Title: Re: Syncronization between h/hpp and c/cpp files
Post by: gtafan on October 22, 2018, 04:22:15 pm
Posibly this feature already exists in codeblocks, but I haven´t found it yet. So what I´d like to have is when I create a void in the h/hpp file the feature should create an empty implementation in the corresponding c/cpp file. Also when changing something on the void in the h/hpp the changes should be also done in c/cpp.

I never noticed this feature; but, I do not use CB as a editor very much.

I would like the first part of creating an empty implementation; but, I would not like the second part.

Tim S.
Sorry my bad english again, have edited my post, hope it is now easier to understand what the second part was really about.