Project config and KMessageBox' dontAskAgainName

Vladimir Prus ghost at cs.msu.su
Tue Jan 24 10:16:32 UTC 2006


On Friday 20 January 2006 18:39, Hamish Rodda wrote:
> On Saturday 21 January 2006 00:24, Jens Dagerbo wrote:
> > On 1/20/06, Hamish Rodda <rodda at kde.org> wrote:
> > > I don't mind what decision is made really, just so long as I have the
> > > option not to be confronted with a dialog every time the debugger
> > > starts.
> >
> > Every time? We're not talking about every time, we're talking about
> > the reasonably exceptional case where the developer attempts to start
> > debugging without having previously built the code (this assuming we
> > can detect this). This sure isn't how I work, except by mistake.
>
> Ok, I was wrong, there is detection of the common case that nothing was
> changed within kdevelop (at least behaviourally, I haven't seen the code).
>
> While I would still prefer a configuration option along the lines of the
> optional automatic rebuild which is available for the run case (and even
> support a tri-state option whereby always prompting the user could be
> selected), I could live with a dialog being presented where there are
> unsaved files in the IDE.

Comitted in revision 501897. If the dialog proves to be too troublesome, I can 
add config option later.

- Volodya




More information about the KDevelop-devel mailing list