Re: Query tool margin

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>
Cc: "pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Query tool margin
Date: 2005-11-04 13:53:35
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC392E@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 04 November 2005 13:48
> To: Dave Page
> Cc: pgadmin-hackers
> Subject: Re: Query tool margin
>
> Use ConvertDialogToPixels.
> I'm still not happy, do we really need this? 999 wouldn't be
> enough, I
> do have bigger scripts. Additionally, screenshots need to be updated.

I ran into the problem very recently when debugging some functions - the
backend helpfully told me where the problems were, but of course, I had
a script, not the function itself in the window that reported the error.
I found myself cutting and pasting the function source into an external
editor to figure out which was line 543 or whatever. It became quite
tedious as I'm sure you can imagine.

I guess I could put the lline/column position of the cursor in the
status bar if you prefer? I had figured it could already get quite full
down there with query timings etc.

(and I wouldn't worry about the screenshots - I doubt anyone will ever
notice).

/D

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Andreas Pflug 2005-11-04 14:03:18 Re: Query tool margin
Previous Message Andreas Pflug 2005-11-04 13:48:27 Re: Query tool margin