Re: Server Status window work

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Server Status window work
Date: 2009-02-26 17:06:31
Message-ID: 937d27e10902260906t6ffd65dapf17e5555dd3b8b31@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Thu, Feb 26, 2009 at 4:49 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Dave Page a écrit :
>> On Thu, Feb 26, 2009 at 4:43 PM, Guillaume Lelarge
>> <guillaume(at)lelarge(dot)info> wrote:
>>
>>> I took a look at this. It doesn't seem to me that it will requires a lot
>>> of work. But using a text control will kill an interesting functionality
>>> (which needs more love, but still the functionality is interesting).
>>>
>>> If you set the log_line_prefix to a specific format, the listview gets
>>> two more columns (timestamp and level). If we change the listview
>>> control with a text control, we will loose this functionality. I would
>>> much prefer to keep it.
>>>
>>> Why do you want to have a text control? to copy part of the log text?
>>
>> Yeah - that was the idea (there's also a bug on Windows - each line
>> ends with a square, which I assume is the <CR>).
>>
>
> Do you need to copy multiple lines? we can use the copy item of the edit
> menu to allow one to copy one or more lines? if you're OK, I'll make a
> patch for this and the Windows bug.

Sure, that would work. It'd be nice to be able to copy any of the
listviews in fact (wouldn't be hard to do I guess - just iterate the
rows and build a string with tab delimited columns and <lf> delimited
rows).

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message svn 2009-02-26 17:11:37 SVN Commit by dpage: r7615 - in trunk/pgadmin3/pgadmin: ctl schema
Previous Message Guillaume Lelarge 2009-02-26 16:49:34 Re: Server Status window work