Re: SVN Commit by dpage: r6765 - in trunk/pgadmin3: . pgadmin/debugger

From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
To: "Dave Page" <dpage(at)postgresql(dot)org>
Cc: <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: SVN Commit by dpage: r6765 - in trunk/pgadmin3: . pgadmin/debugger
Date: 2007-10-22 07:18:13
Message-ID: 01e701c8147b$b5a065e0$c601a8c0@HP22720319231
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Dave.

Oops, I appreciate the help of some problems.:-)
I thought that it was required by the reason for treating PL/pgSQL of hundreds of lines.
Then, The overlapping indicator regarded me as the trifling problem....
Anyway, Thanks!

BTW, This will be improved a little. Does your unpleasant factor disappear?
(v1.9.0)

Regards,
Hiroshi Saito

----- Original Message -----
From: <svn(at)pgadmin(dot)org>

> Author: dpage
>
> Date: 2007-10-19 11:51:14 +0100 (Fri, 19 Oct 2007)
>
> New Revision: 6765
>
> Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6765&view=rev
>
> Log:
> Revert Hiroshi's patch to add line numbers to the margin of the debugger (rev: 6757). They
> are not shown because the breakpoint and execution markers obscure then in quite an ugly
> way, and the cursor line number and execution line numbers are both show in the status bar
> anyway. Fix an off-by-one error in the line numbering while we're here.
>
>
> Modified:
> trunk/pgadmin3/CHANGELOG
> trunk/pgadmin3/pgadmin/debugger/ctlCodeWindow.cpp
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend

Attachment Content-Type Size
ctlCodeWindow_patch application/octet-stream 1.0 KB

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2007-10-22 07:35:08 Re: 1.8.0 Uploaded
Previous Message svn 2007-10-22 05:15:27 SVN Commit by hiroshi: r6784 - trunk/www/download