Version: cvs (using KDE Devel) Installed from: Compiled sources Compiler: g++ 2.95.3 OS: Linux Some annoying bugs still or newly present in Alpha3 (actually CVS from 01/08/2003), developng C++ and using ideal and katepart: 1. Toolbars are still messed up (but you know this). 2. After I reopen a project and I get 5 opened source files, and I select the 3rd, the back button will bring me to the following files: 4th, 5th, 4th, 3th, 2nd, 1st (and now it gets disabled) As I figured out it brings back to the last selected file(s) first and if there is no "last" selected file, switches to the last one and goes back in the opened file list. This is really confusing... And even now, after I've switched (randomly) between the open files, pressing back a lot of time crashed Gideon, altough I couldn't reproduce now, so I will sent the backtrace next time when it crashes. 4. The autocompletion is very annoying now. It's nice that it remembers the typed strings, but: a. ctrl-space does not give me the autocompletion list in some cases (eg. I have a class Foo with static method foo_method), after I type Foo::f and ctrl-space, it will not give me a list with foo_method inside b. pops up automatically after the 3rd entered char, which is nice sometimes, but why cannot I get the same after the first letter with ctrl-space? c. the automatic popup if more than 3 chars are entered is annoyin when you try to undo what you have typed (with Ctrl-Z). It pops up after every Ctrl-Z step and you must press ESC to disappears, otherwise CTRL-Z will not work again. :-( 5. In the files groups view, if a group contains explicit list of files (like GNU: AUTHORS;ChangeLog;COPYRIGHT), they do not appear under this group. It's an older bug. 6. Removing breakpoints during a debug process does not always really remove them, and sometimes the running will break in the line where there was a breakpoint, but I removed it. The only solution in this case is to restart the debugging. (older bug) 7. In the Breakpoints windows, selecting Clear All Breakpoints does not remove all of them... (older bug) 8. If you set a breakpoint eg. at line 100 and later enter some new lines around this line, the breakpoint itself will remain on line 100, but the breakpoint mark is moving down, which becomes confusing during debugging. (and old bug, from KDevelop 2 days) 9. "Toggle Breakpoint" from the RMB menu sets the breakpoint to the current cursor position, not to the line where you clicked with the mouse. Altough this is understandable, it is confusing, eg. if you scroll down with the mouse and try to set a breakpoint, and you realize that it was set some pages before/after... 10. The watch window does not show the current function/method's symbols when a breakpoint is reaches until you select the function from the Frame Stack. Once you've done it, during the following debugging processes it will came up automatically (even if you don't use the Frame Stack), just as in KDevelop 2, until you restart Gideon... I think it should show the current function's symbols right from the start. (older Gideon bug) 11. Watched variables are not remembered between debugging sessions. This is really bad and slows down the debugging. (and old bug from KDevelop 2 days). 12. When using builddir!=srcdir in developing, you must still make a symling from srcdir to the executable in builddir, otherwise you cannot debug. Why not just use the setting from Project Options also when debugging? (old bug, already reported) 13. Running an app from Gideon still does not enable the stop button/menu. Debugging does. 14. Running/debugging the app if the sources were modified does not rebuild the executable. You must explicitely rebuild it. I got used to it by now, but it should be taken as a bug.... 15. Bookmarks and Build accelerators are clashing (&B). + some important actions does not have keyboard shortcuts (run, debug, step, trace, etc.) 16. In File Tree the directories are not shown first, but mixed between files. Hard to find them... 17. In Classes View, clicking onto a class method opens both the header and the implementation file. I'm not sure it is ok, as you can open the header by clicking onto the class name, or RMB->Go To Declaration. 18. If you browse the documentation from the search results, the links are opened in a new window. If you do it from the Doc. Browser, they aren't. This is inconsistent. The back button in the latter case does not bring me back to the previous browsed doc. page. Annoying. (old bugs, I think already reported) Ok, this is for now, tell me if you need some more help. Sorry again for sending lot of bugs in one report. You know, dial-up connection... Andras
And addition: 19. The Application Output window does not show the last outputted line, but show the lines what were previously displayed. You must scroll down manually every time. The ideal behaviour would be that it scrolls automatically, so you see the last line, if you wathched the last line(s), but does not scroll automatically if you click on a line. Just look at how the Messages window behaves during compilation. ;-)
Would you like to handle 19 bugs within one report for Quanta? Please file separate bug reports in future (or post to kdevelop-devel?).
Subject: Re: 18 Bugs in Alpha3 I would try... Yes, I know this may be annoying, especially as the bugs should possibly be assigned to different developers, but I had two (real) choices: post them in one bug report or send them to the list. I picked up the first one, as this way it won't "get lost", but unfortunately I picked up the wrong one. Posting 19 bugs using a web interface is a real pain and money consuming if you have a dial-up connection, even if you write the report content offline. And the number of online minutes / month is limited for me. Sorry for this, I don't believe that I will ever send so much bug to a project, but KDevelop is one of the projects I like and use very often. Right now I don't send the same reports to the mailing lists, but in the future if it ever happens, I will do so, if you say so. Andras On 2003. January 09., Thursday 14:45, you wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=52788 > > > > > ------- Additional Comments From binner@kde.org 2003-01-09 13:45 ------- > Would you like to handle 19 bugs within one report for Quanta? > Please file separate bug reports in future (or post to kdevelop-devel?).
Created attachment 778 [details] Partial fix for #5.
The attached patch fixes partly the bug #5, so there can be defined groups with "foo.*" pattern, not just pattern started with *. It still does not find the GNU files, like AUTHORS, as those files are not even tested if they are in a group or not... As I figured out, the "m_part->project()->allFiles();" does not return the top level files! There is a need to fix it in the project part. Andras
Somebody split this bug report please!!! I've added a lot of components so it should be easier. There are parts for which there aren't components yet, but you can add them of course.
Closing this bug report as INVALID - assigning existing bug reports to new separate bugs. I tried to not put in duplicates. If I missed one, someone please open it.
Subject: Re: 18 Bugs in Alpha3 Ok, I just hope that none of the still valid bugs will be forgotten (I committed the fix for some of those in the meantime). Andras