Version: 3.0.3 (using KDE KDE 3.2.2) Installed from: Gentoo Packages OS: Linux When I create a new class using the class wizard, I have to manualy open the generated cpp and h files. Which to me seems pointless. When I create a new class, I'm going to edit it afterwards, so the files could just as well be opened automaticly (as when creating a new file in the editor). I'm using Kate part editor. (I really can't believe this havn't been reported before? However, I can't find any bugs regarding this)
This is not a bug, this is a feature. KDevelop does not open files you create.
Why did you close it? This seems very relevant to me, and I also reported it as a feature... You say that KDevelop does not open files I create, however it does when I create a file with the "New file wizard", but it doesn't open autogenerated files. Given the fact that two people have already voted on this (and that's not including me), it seems very unappropriate to just close it as WONTFIX... If you still mean this is not a valid feature request close it again, but I'm reopening it.
As one of the voters I guess I should put my $0.02 US in on this. If the objective is to close out bugs, I say let it stay closed for the time being. If it wasn't originally categorized as a wishlist item, and that's why it was closed. Then I say leave it as a wishlist item. There are far more important features that need attention - IMO. This (feature) is just one of the little things I find unintuitive.
Another cent from the other voter: each time creating a new class using the wizard I'm surprised that the files don't pop up - I sometime spent up to 5 seconds waiting and wondering ...
I voted for this too, cause it is indeed very unintuitive, and it shouldn't ask more than five minutes to fix it. And it was in kdevelop before, don't know why they removed the "feature". P.S. In my case, it's actually in the qmake manager that the new files aren't opened automatically, but I guess it's the same bug
I could fix this myself if someone could tell me how to get the partController() object from within the CppNewClassDialog::ClassGenerator::generate() method...
*** This bug has been confirmed by popular vote. ***
I just added my vote as well. I find this one of the most annoying things in KDevelop(which I love overall!) at this point. Every time I create a new class I expect it to open in the editor, then curse and start searching it in the file or class tree. Even after using KDevelop for a long while I cant get used to this. There really should be an option to allow for this instant opening behaviour.
No, there really shouldn't be an _option_. IMHO, KDevelop should simply open the newly created files. I'm pretty sure the user intends to edit them further in almost any reasonable scenario. Maybe there is a technical reason this isn't as easy as it would seem though, I haven't checked.
today it's 2005-06-27 -- in other word a bug that's annoying, unreasonable and easy to fix stays open for over year now only because sombody thinks it should remain as default behaviour, ignoring the request to make it at least configurable (although as said befor it's not really intuitive) and thus imposing his point of view to other users. nice. just my 2c.
Arne, PLEASE provide a patch.
i'm no experienced c++programmer and i never really looked into the kdevelop code, but well, if you give me some hints were to find the code for the wizzard (and maybe how to open files with katepart) i'll try to look into next weekend. if there's to much work and you classifiy a request thus as of minor importance, wouldn't it be better to introduce a status to reflect this?
Arne, the documentation is at: http://www.kdevelop.org/HEAD/doc/api/html/ The things you want are: http://www.kdevelop.org/HEAD/doc/api/html/classFileCreatePart.html http://www.kdevelop.org/HEAD/doc/api/html/classClassViewPart.html
Amilcar, I'm an old hacker of the ClassViewPart. This behavior is contrary to the behavior of every IDE that I know of, and it is a useless "feature", because 99% of the time people will actually want to edit a file they have created. Please fix this bug, or I can fix it in the SVN but it's a pain to compile kdevelop (I know :D )
Fixed in 3.4 branch.