Re: Paste rows patch - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Paste rows patch
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E401388019@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Paste rows patch  ("Edward Di Geronimo Jr." <edigeronimo@xtracards.com>)
Responses Re: Paste rows patch
List pgadmin-hackers

> -----Original Message-----
> From: pgadmin-hackers-owner@postgresql.org
> [mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of
> Edward Di Geronimo Jr.
> Sent: 09 May 2006 15:00
> To: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] Paste rows patch
>
> Quoting Dave Page <dpage@vale-housing.co.uk>:
>
> > It's looking much better, however, I still think that if
> the cursor is
> > actually active in a cell then the paste should go to that
> cell, and
> > only in other cases to the new row. On Windows, the only way to do
> > that is ctrl-v or right-click->paste. The paste button and ctrl-v
> > should always do the same thing (though I wonder if that's an issue
> > with Windows doing the actual paste operation in the ctrl-v
> case) imo.
>
> I forgot about that issue. I think you're right, however, I
> don't really know how to solve it. I think the solution is to
> detect if the cursor is in an edit box, and call the edit
> box's Paste function if so, however, I'm not sure how to tell
> if we're in an edit box or not.

We enable/disable the save button on the entry/exit of a cell - see
frmEditGrid::OnEditorShown() & frmEDitGrid::OnSave(). Does that look
robust enough to use to set a flag?

Regards, Dave.

pgadmin-hackers by date:

Previous
From: svn@pgadmin.org
Date:
Subject: SVN Commit by dpage: r5139 - trunk/pgadmin3/xtra/wx-build
Next
From: Andrew Lazarus
Date:
Subject: Re: [pgadmin-support] Segmentation fault in GUI