Re: SVN Commit by dpage: r4380 - in trunk/pgadmin3:

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: SVN Commit by dpage: r4380 - in trunk/pgadmin3:
Date: 2005-07-21 21:30:37
Message-ID: 42E013FD.3090204@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
>>Sent: 21 July 2005 15:00
>>To: Dave Page
>>Cc: pgadmin-hackers(at)postgresql(dot)org
>>Subject: Re: [pgadmin-hackers] SVN Commit by dpage: r4380 -
>>in trunk/pgadmin3: . src/dlg
>>
>>
>>
>>>You miss the point. If you're trying to put your columns in
>>
>>a specific
>>
>>>order (yes, I know it doesn't matter from a theoretical POV,
>>
>>but some of
>>
>>>us like things to look nice as well), you have to remove all
>>
>>the other
>>
>>>thirty, and start again.
>>>
>>>
>>>
>>
>>And this will happen exactly how often?
>>In contrast to annoying mbxes popping up with a kloing! at a
>>rate of 20/min.
>
>
> You delete 20 columns a minutes? If you don't like it, turn off the
> confirm delete option. Oh, you did already didn't you? :-)
>
> It has happened to me on more than one occasion, and I have had reports
> of this before,

Until now, the message boxes where about warning the user to prevent
(more or less) severe damage, not dullness. I'm strongly against moving
further into that direction.

Regards,
Andreas

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2005-07-28 10:00:19 Role support
Previous Message Dave Page 2005-07-21 14:03:33 Re: SVN Commit by dpage: r4380 - in trunk/pgadmin3: . src/dlg