Обсуждение: Inconsistent editing behavior.

<div class="Section1"><p class="MsoNormal"><font face="Arial" size="2"><span style="font-size:10.0pt;
font-family:Arial">I have been working with PGAdminIII v1.6.1. and 1.6.2 for the past three days and discovered a
problemwhile editing. To reproduce the error, open the editor window to edit an existing object. Then, place the
insertionpoint with the mouse somewhere where you want to edit the document. For the sake of testing just enter
comments.Enter some text. Then, try to move the insertion point with the keyboard arrows. And insert some more text. If
itworks, repeat the process. Eventually you will notice that you are typing where you thought you would
be.</span></font><pclass="MsoNormal"><font face="Arial" size="2"><span style="font-size:10.0pt; 
font-family:Arial"> </span></font><p class="MsoNormal"><font face="Arial" size="2"><span style="font-size:10.0pt;
font-family:Arial">I am using Windows XP SP2 with all known updates (except IE 7). This installation just happens to be
ona Microsoft Virtual PC 2004 instance that runs on Windows XP SP2 but I have been using PGAdminIII v1.4.3 for several
monthson the same machine without any problems.</span></font><p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size:10.0pt;
font-family:Arial"> </span></font><p class="MsoNormal"><b><i><font face="Times New Roman" size="2"><span
style="font-size:10.0pt;font-weight:bold;font-style:italic">PatrickHeadley<br /></span></font></i></b><font
size="2"><spanstyle="font-size:10.0pt">Linx Consulting, Inc.<br /> (303) 916-5522<br /><a
href="mailto:LinxConsulting@comcast.net">LinxConsulting@comcast.net</a><br/><a
href="http://www.linxco-inc.com">www.linxco-inc.com</a></span></font><pclass="MsoNormal"><font face="Times New Roman"
size="3"><spanstyle="font-size: 
12.0pt"> </span></font></div>

Patrick Headley wrote:
> I have been working with PGAdminIII v1.6.1. and 1.6.2 for the past three 
> days and discovered a problem while editing. To reproduce the error, 
> open the editor window to edit an existing object. Then, place the 
> insertion point with the mouse somewhere where you want to edit the 
> document. For the sake of testing just enter comments. Enter some text. 
> Then, try to move the insertion point with the keyboard arrows. And 
> insert some more text. If it works, repeat the process. Eventually you 
> will notice that you are typing where you thought you would be.

I can't see any problem in testing. I'm not clear form your description 
what the problem is either though - even your last sentence implies that 
it is working correctly.

Regards, Dave.

Patrick Headley wrote:
> The problem is intermittent and, to my knowledge is new to v1.6.0. I see
> that I confused version numbers in my first email. The problem is showing up
> in v1.6.0 and 1.6.1. Also, now that I reread the last line I typed I see
> that I typed it in wrong. What I intended to say was that eventually you
> will notice that the insertion point is not where you expected it to be.

hmmm, I don't suppose you are actually seeing this known bug?

[STC] On wxMSW 2.6.3 with Num Lock turned off, the control functions      (arrows, insert/delete etc) of the numeric
keypaddo not work.      wxWidgets bug ref 1529525.
 

> I just tried to reproduce the problem but was unsuccessful. It may be that I
> haven't worked in PGAdminIII for long enough in this session. If I get the
> strange behavior again I'll document it some more and send you an update.

Thanks.

> Something else that just came to mind that may be related. In v1.4.3 I have
> noticed that the keyboard shortcuts CTRL-V and CRTL-C stop working. This too
> is intermittent and occurs less than the problem I first emailed you about.
> It's also less annoying because the problem is obvious when it occurs and
> the pop-up menu continues to work.

I use CTRL-V and CTRL-C daily on XP Pro and have not seen this issue 
either. Perhaps you have coffee in your keyboard? :-)

Seriously though, if you can figure out what might trigger this 
behaviour it would certainly help me figure out what to fix.

Regards, Dave.