I believe there is a Qt Creator plugin for that, but I am not quite sure.

I am not sure when this was introduced (before 2.1 feature freeze or afterwards): Add a method to a .h file, move cursor on the method name and hit Alt-Enter.

Not really obvious, I agree. The refactoring indicator is still missing in C++ files.

I am not aware about anything for the getter/setter methods though.

Works in my 2.1.0 RC, so I guess it was before ;-)

Good to know! I would have expected this to appear in the context menu for the declaration though, instead of the Switch Between Method Declaration/Definition item if there is no definition yet.

Andre: But then it would be too obvious:-)

Technically it is a C++ Quick Fix operation and we trigger those by Alt-Enter. There are more (like make a char array translatable, turn one into a QLatin1String, etc.), but as I said before: The indication when those can be triggered are still missing… which would make this really nice feature way more useful since people actually have a chance to find it.

Ok thanks Tobias, this was pretty helpful and I guess I should have to get on it by myself.
But yes it isn’t really obvious ; )

I’m wondering if there is no one else missing the auto add of getter and setter methods because they took much time.

I would be really interessted in that kind of helpers.

I do miss automatic generation of getter and setter method, but I would like to see them being auto-generated by the Q_PROPERTY macro.

Thats a nice idea, as far as i can affect the behavior of these methods.

Schneidi wrote:

Thats a nice idea, as far as i can affect the behavior of these methods.

Obviously. I was thinking about something like this:

The idea is that you specify the member variable to use, and that the macro can generate the getter, setter and/or the signal by using a different keyword than the standard READ and WRITE. In this case, the read method would not be generated, but the write and the signal would be.

Ok, but this approach would generate the most basic kind of getter and setter methods right ?
This is a nice way to save much time for basic member access.

IMHO it would be enough to generate the mutator methods. If I want to add more logic to these methods i guess that would be a good and easy to maintain approach.

Other IDEs already offer these features. The Creator is a fantastic piece of software but there are some nice features missing yet.

Yes, that is the idea. I guess having QtCreator generate the methods would already be a big help, but having them generated by Q_PROPERTY would be more maintainable. Deleting the Q_PROPERTY also gets rid of the generated methods that way.

You guys are developers, so I am looking forward to your Merge Requests about those helpers;-)

Seriously: It is not that hard to write them, using the existing examples as a guide. http://qt.gitorious.org/qt-creator/qt-creator/blobs/master/src/plugins/cppeditor/cppquickfixes.cpp has most of the code of the existing ones.

I just might… But first, I am going to see how a previous merge request is going to fare. I know it is my turn now for that request, but I have seen others stalled for about a year. Thanks for the ALT-Enter tip though!

Believe it or not,

I take this into consideration, but if there is already such a plug-in or whatever why should I do another.
But at the moment my skills arn’t at the level to write plug-ins for the creator.

Maybe in the near future ^^

Andre: We try to process MRs as fast as possible, but sometimes they do stall:-( The people doing the reviews are the developers that work on creator. Unfortunately we all are rather swamped with work… We try to keep up, but some MRs fall through the cracks, others are reviewed but awaiting action by the submitters. Gitorious does not send notification on updates to MRs, so sending a mail to the reviewer does help getting your MRs through the review faster.

Feel free to send me a message if you feel your MR did not get the attention it deserved. I’m happy to poke my coworkers;-)

Schneidi: Quickfixes should just be a couple of lines of code, no need to put those into a separate plugin.