[Bug 64279] kdevelop doesnt store some global/project settings

[Robert Shideleff]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=64279     




------- Additional Comments From bigbob at shideleff.com  2003-11-07 15:40 -------
Subject: Re:  kdevelop doesnt store some global/project settings

Amilcar do Carmo Lucas wrote:

>------- You are receiving this mail because: -------
>You are a voter for the bug, or are watching someone who is.
>     
>http://bugs.kde.org/show_bug.cgi?id=64279     
>
>
>
>
>------- Additional Comments From a.lucas at tu-bs.de  2003-11-07 10:44 -------
>"the executable, don't *seem* to get saved"
>
>If the path to executable is to be absolute then it MUST start with / otherwise it gets cleaned up. This is not a bug! The GUI is explicit enough!
>
>Again, can you be more specific about what other options do not presist?
>  
>
It's not absolute. The GUI above says that it is relative from the build 
directory. There are three radio button selects there. the one chosen by 
default is 'relative from build directory'. So I simply typed in the 
name of the executable. I obviously typed in the correct name with the 
correct path (which is no path in this case), since (as stated before) I 
CAN debug the executable. In other words, gdb got called with the 
correct parameters to find the executable. Its just that when I enter 
the dialogue again it gets lost.

In any case, isn't it sort of counter-intuitive that the GUI will 
actually destroy something that I typed in explicitly without at least a 
dialogue or something? What if I had typed in the absolute path on 
purpose, but clicked the wrong radio button? I'd get pretty annoyed with 
having to fix both the radio button and the path (again). Possibly even 
more annoyed than I get right now when I have to type in the executable 
name again when it was obviously working as entered last time.