Version: 3.0.0a7 (using KDE 3.1.1) Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB If you left click on a file in Automake Manager that does not exist in the "src" directory (e.g. "myappiface.skel"), there is no error message and Automake Mana ger just silently closes.
Sorry, can not reproduce this one!
Subject: Re: Non-existent file causes Automake Manager to terminate prematurely Did you try creating a new project, as in bug 65362, then left-click on "<appname>iface.skel" file? Otherwise, try adding a file to the project in Automake Manager (AM) and deleting it in the Shell in another window. When you left-click on the filename in AM Detail View, AM closes, with no error message. Note: This is not an artificial situation. A user might easily delete (or rename?) a file, accidentally or deliberately, outside Gideon. AM should protect itself and the user against further consequences of this loss of integrity in the Makefile.am. Hence my bug report.
> Did you try creating a new project, as in bug 65362, then left-click > on "<appname>iface.skel" file? yes. > Otherwise, try adding a file to > the project in Automake Manager (AM) and deleting it in the Shell > in another window. did that. > When you left-click on the filename in AM Detail View, AM closes, with no > error message. What do you mean by closes? Nothing happens here! That is why I unconfirmed the bug. Until someone else confirms it it sould be left unconfirmed. Thanks for the detailed report though.
Subject: Re: Non-existent file causes Automake Manager to terminate prematurely > > Did you try creating a new project, as in bug 65362, then left-click > > on "<appname>iface.skel" file? > yes. So, what happens in your environment then? Do you get an error message? Does a "file" open? Does the Automake Manager window stay open? The answers for me are no, no and no. > > When you left-click on the filename in AM Detail View, AM > > closes, with no error message. > What do you mean by closes? Nothing happens here! > Automake Manager window closes. To go on working in AM I have to click again on the tab at the right of the Ideal-mode window. I am using SuSE 8.2, KDE 3.1.1, Qt 3.1.1 and Gideon a7, downloaded 29/9/03.
> So, what happens in your environment then? Do you get an > error message? Does a "file" open? Does the Automake Manager > window stay open? The answers for me are no, no and no. No error message. The file doesn't open. The Automake Manager window stays open. No crash. > Automake Manager window closes. To go on working in AM I have to > click again on the tab at the right of the Ideal-mode window. THIS IS NORMAL! The same thing happends if you click on ANY file in the automake manager. Unless you select the (.) icon on the top left corner of the Automake manager window it will always colapse after a click. Colapse is different from close. I thought (reading your initial bug report) that AM crashed and closed it's window. But It's looks like all it does is to colapse the window like it is supposed to. So I guess this bug resumes to: Automake Manager doesn't issue an error/warnig for non-existent project file(s)
Subject: Re: Automake Manager doesn't issue an error/warnig for non-existent project file(s) Re "normal" closing of the AM window. File Selector, File Tree, Classes and File Groups all stay open and allow you to open more files - a useful feature for program files. ANY piece of software should remain open, if it can, in an error situation - allowing the user to correct the error or live with it. I seem to remember, Amilcar, that you corrected me on that point regarding KGoldrunner failing to find its user documentation ... :-) Re AM does not report a non-existent file: yes, that's a bug and should be handled better. Re inconsistency with File Tree, etc: should I report another bug? > Unless you select the (.) icon on the top left corner of the > Automake Manager window it will always collapse after a click. > Collapse is different from close. > Well, I've used AM extensively for about 3 months now and never noticed that button. It's rather inconspicuous ...
> should I report another bug? no. Now that you noticed the button, do you understand my #5 comment?
I always understood your comment #5, but I never noticed the button: you pointed it out to me! I think whether the window collapses or not may come down to the defaults KDevelop 3 developers choose for that button. They ought to be consistent across all windows, not one thing for File Tree and another for Automake Manager. My preference would be for the default to be no collapse after opening a file, since I often want to look at more than one file and it is easy to close the sidebar if it is in the way.
Hardly a big problem. Changed to 'minor'.
This is fixed in 3.4, we don't do anything now when trying to open non-existant files.