bernd at physik.hu-berlin.de
Mon Jul 3 22:03:46 UTC 2000
On Tue, 4 Jul 2000, John Birch wrote:
> On Tue, 04 Jul 2000, you wrote:
> > Am Mon, 03 Jul 2000 schrieben Sie:
> > > What should the stop button do?
> > >
> > > 1) Stop a compilation
> > > 2) Stop a program run
> > > 3) Stop a program run in the debugger
> > > 4) Stop a full text search
> > > 5) Stop a grep
> > >
> > > or any combination of these :-)
> > I think a "Stop" should stop everything. If not we must provide 4-5
> > Stopbuttons, and I my opinion this isn't a good idea.
> What about raising an event - (I think I saw something about that in the
> docs) Then the part is responsible for stopping (or not as the case may be)
There is compilationAborted() which in fact stops everything right now :-)
Maybe renaming it to stopButtonClicked() would be advantageous.
One could even make it configurable on a per-part basis ... I'll rewrite
the configuration dialog framework in the next days, then we'll see :-)
More information about the KDevelop-devel