Re: Paste rows rough patch

> -----Original Message-----
> From: pgadmin-hackers-owner@postgresql.org
> [mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of
> Edward Di Geronimo Jr.
> Sent: 03 May 2006 16:31
> To: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] Paste rows rough patch
>
> Dave Page wrote:
>
> >Hmm, I'm seeing some odd behaviour...
> >
> >- A copy/paste of a single row seems to work in most cases, but:
> >
> >  - Sometimes, nothing got pasted into the new row
> >  - Sometimes, the entire row got pasted into the end of an existing
> >cell (which had been selected, prior to selecting the '*' row.
> >
> >
> The code does the pasting based on the grid cursor position,
> which wx tracks seperately from the highlighted selection. If
> you have the cursor in say row 10, then click the * to
> highlight the * row, the cursor stays in row 10. If you then
> hit paste, the data will go into row 10. Does that help
> explain things?

Certainly explains it, but I'm sure it will confuse the heck out of some
users.

In testing on Windows, I see that a cell can be active (ie. Have a thick
border), or have focus (ie. The cursor is flashing in it). It seems to
me that we should only paste directly into the cell in the latter case -
in the former, or any other case, the paste goes to the '*' row. Is that
doable? Does it sound sensible to you?

> >- Multi-row pasting doesn't work, but I guess you know that!
> >
> >
> I wasn't planning on handling that case. I didn't even want
> to think about how to handle the data validation issues on
> that case. It would only really be useful on tables with no
> primary key or a (when I'm
> finished) a serial primary key. I've gotten the feeling that
> pasting multiple rows is going to be a big ordeal to
> implement, and therefore wasn't planning on doing it.

OK, np.

Cheers, Dave.