Re: CVS Commit by dpage: Allow query cancel/terminate
От | Dave Page |
---|---|
Тема | Re: CVS Commit by dpage: Allow query cancel/terminate |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E40C3694@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | CVS Commit by dpage: Allow query cancel/terminate (cvs@cvs.pgadmin.org) |
Ответы |
Re: CVS Commit by dpage: Allow query cancel/terminate
|
Список | pgadmin-hackers |
> -----Original Message----- > From: Andreas Pflug [mailto:pgadmin@pse-consulting.de] > Sent: 22 June 2004 14:35 > To: Dave Page > Cc: pgadmin-hackers@postgresql.org > Subject: Re: [pgadmin-hackers] CVS Commit by dpage: Allow > query cancel/terminate > > cvs@cvs.pgadmin.org wrote: > > >Log Message: > >----------- > >Allow query cancel/terminate > > > > > > > > Hm, > I'm not too happy about "Hi there, I did it" message boxes. I think they are needed as sending signals doesn't always work, or they may be a slight delay before they get handled - you need something to stop the user clicking the button repeatedley if things don't happen instantly. > Do we need that at all? Then we should add a status bar. > Should we use wxDEFAULT_NO on the security question msg box? Probably, I'll add that. > IMHO cancel/terminate is also usable on the locks page, so > the buttons could go to the top line. Hmm, I guess so. I'm inclined to leave them at the bottom though as the top will be getting crowded. Bottom should be reminiscent of the Windows task manager... Might have to wait 'till tomorrow for that one. BTW, on the restore dialogue, the 'contents' tab doesn't seem to do anything useful (nor for that matter does the view button). Regards, Dave.
В списке pgadmin-hackers по дате отправления: