Обсуждение: Cannot paste text from eclipse 3.5 to PGAdmin III

I'm having problems pasting text from Eclipse 3.5 into PGAdmin III (1.10.0 and 1.8.4) on Mac OS X.<br /><br />I have
reporteda bug to eclipse which describes the full issue <a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=284329">https://bugs.eclipse.org/bugs/show_bug.cgi?id=284329</a><br
/><br/>I was wondering if there is anything that can be done in PGAdmin III to get the clipboard to work?<br /><br
/>Cheers,<br/>Paul<br /> 

Also, along the lines of pasting...

You can't copy text from a query editor using the "select a region" 
method that's standard in X (where you select a bit of text, and then 
middle click in another window to paste).. This kills the ability to 
paste into xterms from the query window.  But, if you ctrl-c the query 
text, and paste it into the scratch pad, and *then* select from the 
scratch pad.  You can middle click paste into an xterm.




On 07/30/09 17:35, Stephan Jaensch wrote:
> Hi Paul,
>
> Am 30.07.2009 um 18:14 schrieb Paul Austin:
>
>> I'm having problems pasting text from Eclipse 3.5 into PGAdmin III 
>> (1.10.0 and 1.8.4) on Mac OS X.
>>
>> I have reported a bug to eclipse which describes the full issue 
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=284329
>>
>> I was wondering if there is anything that can be done in PGAdmin III 
>> to get the clipboard to work?
>
> I'm having the same issue here on two different Macs. If there is 
> anything the PgAdmin developers need me to do to help, please let me 
> know...
>
> Cheers,
> Stephan

On Fri, Jul 31, 2009 at 11:25 PM, Mark Murawski<kobaz@kobaz.net> wrote:
> Also, along the lines of pasting...
>
> You can't copy text from a query editor using the "select a region" method
> that's standard in X (where you select a bit of text, and then middle click
> in another window to paste).. This kills the ability to paste into xterms
> from the query window.  But, if you ctrl-c the query text, and paste it into
> the scratch pad, and *then* select from the scratch pad.  You can middle
> click paste into an xterm.

Unfortunately we're largely at the mercy of the version of the
Scintilla text control that wxWidgets ships when it comes to
copy/paste. We are looking into ways we might update it independently
however, as there are other issues that are fixed in the upstream
sources that haven't made it into wxWidgets yet.

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

On Mon, Aug 3, 2009 at 4:34 PM, Stephan Jaensch<sjaensch@gmx.net> wrote:
> Hi all,
> Am 30.07.2009 um 18:14 schrieb Paul Austin:
>
> I'm having problems pasting text from Eclipse 3.5 into PGAdmin III (1.10.0
> and 1.8.4) on Mac OS X.
>
> I have reported a bug to eclipse which describes the full issue
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=284329
>
> I was wondering if there is anything that can be done in PGAdmin III to get
> the clipboard to work?
>
> After further investigation using the Clipboard Viewer from Apple's
> development tools, it seems that PGAdmin ist inserting the UTF16 version of
> the clipboard contents instead of using the UTF8 version, stopping at the
> first NUL byte.
> Is this a wxwidgets or PGAdmin bug?

wxWidgets. pgAdmin just uses the wxTheClipboard class, which fetches a
wxString for us.

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

Hi Dave,

Am 03.08.2009 um 17:57 schrieb Dave Page:

>> After further investigation using the Clipboard Viewer from Apple's
>> development tools, it seems that PGAdmin ist inserting the UTF16  
>> version of
>> the clipboard contents instead of using the UTF8 version, stopping  
>> at the
>> first NUL byte.
>> Is this a wxwidgets or PGAdmin bug?
>
> wxWidgets. pgAdmin just uses the wxTheClipboard class, which fetches a
> wxString for us.

Seems to be fixed in the next wxWidgets version: http://trac.wxwidgets.org/ticket/10902

Cheers,
Stephan

On Tue, Aug 4, 2009 at 8:50 AM, Stephan Jaensch<sjaensch@gmx.net> wrote:
> Hi Dave,
>
> Am 03.08.2009 um 17:57 schrieb Dave Page:
>
>>> After further investigation using the Clipboard Viewer from Apple's
>>> development tools, it seems that PGAdmin ist inserting the UTF16 version
>>> of
>>> the clipboard contents instead of using the UTF8 version, stopping at the
>>> first NUL byte.
>>> Is this a wxwidgets or PGAdmin bug?
>>
>> wxWidgets. pgAdmin just uses the wxTheClipboard class, which fetches a
>> wxString for us.
>
> Seems to be fixed in the next wxWidgets version:
> http://trac.wxwidgets.org/ticket/10902

Ahh, well spotted. Unfortunately it'll be at least 1.12 before we move
to the stable branch of wxWidgets that fix will go into though. I have
a sneaking suspicion we may end up patching wxWidgets...

I've created a pgAdmin ticket for this: http://code.pgadmin.org/trac/ticket/13

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

Le mardi 4 août 2009 à 09:50:38, Stephan Jaensch a écrit :
> Hi Dave,
>
> Am 03.08.2009 um 17:57 schrieb Dave Page:
> >> After further investigation using the Clipboard Viewer from Apple's
> >> development tools, it seems that PGAdmin ist inserting the UTF16
> >> version of
> >> the clipboard contents instead of using the UTF8 version, stopping
> >> at the
> >> first NUL byte.
> >> Is this a wxwidgets or PGAdmin bug?
> >
> > wxWidgets. pgAdmin just uses the wxTheClipboard class, which fetches a
> > wxString for us.
>
> Seems to be fixed in the next wxWidgets version:
> http://trac.wxwidgets.org/ticket/10902
>

We are not yet compatible with 2.9.0. I began the work on that, but I'm afraid
this will be a hard work.


--
Guillaume.http://www.postgresqlfr.orghttp://dalibo.com

On Tue, Aug 4, 2009 at 9:07 AM, Guillaume Lelarge<guillaume@lelarge.info> wrote:
>
> We are not yet compatible with 2.9.0. I began the work on that, but I'm afraid
> this will be a hard work.

That's what I was afraid of. I've heard they've done some pretty major
redesign (hence the planned move from 2.x.x to 3.x.x).

If we do move, I suspect we'll end up chasing new wxWidgets bugs for
months to come as well. I was toying with the idea of keeping our own
set of wxWidgets patchs, as there's also a nasty issue with the STC
that Ashesh and Hiroshi have started looking into, but that doesn't
help on platforms like Ubuntu and Fedora where users will be using the
stock wxWidgets packages- and I whilst I could live with rolling our
own custom wxWidgets tarball, I certainly don't want to do RPMs and
DEBs etc.

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

On Tue, Aug 4, 2009 at 9:07 AM, Guillaume Lelarge<guillaume@lelarge.info> wrote:
>
> We are not yet compatible with 2.9.0. I began the work on that, but I'm afraid
> this will be a hard work.

That's what I was afraid of. I've heard they've done some pretty major
redesign (hence the planned move from 2.x.x to 3.x.x).

If we do move, I suspect we'll end up chasing new wxWidgets bugs for
months to come as well. I was toying with the idea of keeping our own
set of wxWidgets patchs, as there's also a nasty issue with the STC
that Ashesh and Hiroshi have started looking into, but that doesn't
help on platforms like Ubuntu and Fedora where users will be using the
stock wxWidgets packages- and I whilst I could live with rolling our
own custom wxWidgets tarball, I certainly don't want to do RPMs and
DEBs etc.

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

On Tue, Aug 4, 2009 at 10:14, Dave Page<dpage@pgadmin.org> wrote:
> On Tue, Aug 4, 2009 at 9:07 AM, Guillaume Lelarge<guillaume@lelarge.info> wrote:
>>
>> We are not yet compatible with 2.9.0. I began the work on that, but I'm afraid
>> this will be a hard work.
>
> That's what I was afraid of. I've heard they've done some pretty major
> redesign (hence the planned move from 2.x.x to 3.x.x).
>
> If we do move, I suspect we'll end up chasing new wxWidgets bugs for
> months to come as well. I was toying with the idea of keeping our own
> set of wxWidgets patchs, as there's also a nasty issue with the STC
> that Ashesh and Hiroshi have started looking into, but that doesn't
> help on platforms like Ubuntu and Fedora where users will be using the
> stock wxWidgets packages- and I whilst I could live with rolling our
> own custom wxWidgets tarball, I certainly don't want to do RPMs and
> DEBs etc.

If we have our own, couldn't we just link statically?

That said, I bet they have *other* patches in that are specific to
their distribution - they often do. And having to somehow end up
having to merge these things back and forth doesn't sound particularly
entertaining.

-- Magnus HaganderSelf: http://www.hagander.net/Work: http://www.redpill-linpro.com/

On Tue, Aug 4, 2009 at 1:39 PM, Magnus Hagander<magnus@hagander.net> wrote:
> If we have our own, couldn't we just link statically?

We can, but the distros don't usually allow that for their packages.

> That said, I bet they have *other* patches in that are specific to
> their distribution - they often do. And having to somehow end up
> having to merge these things back and forth doesn't sound particularly
> entertaining.

No, quite.

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

Thanks everyone for finding out the cause of the problem. I'll look forward to when the new version of wxWidgests can
beintegrated. Until then I have my TextEditor work around<br /><br />Thanks,<br />Paul<br /><br />