dpage@postgresql.org wrote:
> Erwin Brandstetter wrote:
>> Hi developers! Hi Dave!
>>
>> Testing bet4, rev. 5567:5572 on Win XP
>> I found a couple of quirks in the edit grid.
>>
>> - If I mark part of the text in a field and press <del> only first
>> character of the marked text gets deleted. One would expect all of
>> the marked text to be deleted. (That's what happens if I press the
>> <back> key)
>
> Fixed in SVN.

In RC1, the problem seems to be present still. <DEL> only deletes the
first character of the marked text.


Regards
Erwin

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Erwin Brandstetter wrote:
> dpage@postgresql.org wrote:
>> Erwin Brandstetter wrote:
>>> Hi developers! Hi Dave!
>>>
>>> Testing bet4, rev. 5567:5572 on Win XP
>>> I found a couple of quirks in the edit grid.
>>>
>>> - If I mark part of the text in a field and press <del> only first
>>> character of the marked text gets deleted. One would expect all of
>>> the marked text to be deleted. (That's what happens if I press the
>>> <back> key)
>>
>> Fixed in SVN.
>
> In RC1, the problem seems to be present still. <DEL> only deletes the
> first character of the marked text.

RC1 was rev 5577, the delete fix was rev 5579.

http://svn.pgadmin.org/cgi-bin/viewc...=5577&view=rev
http://svn.pgadmin.org/cgi-bin/viewc...=5579&view=rev

:-)

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Hi developers! Hi Dave!

Testing RC1. Client is Win XP. Server is Debian Sarge.

I have come across a peculiar effect while editing boolean fields. With
other fields, if you want to discard your changes while editing a field,
you hit <esc> and the original value is back (as long as you haven't
saved yet). Not so with boolean fields. Pressing <esc> leaves yields
seemingly random results.
One of the most peculiar show cases:
I click with the mouse. Value is TRUE.
1st click only sets the focus.
2nd click --> NULL
3rd click --> FALSE
4th click --> TRUE (again)
If I hit <esc> now, I end up with FALSE (!). That wouldn't be by design,
would it?

Regards
Erwin



---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Erwin Brandstetter wrote:
> Hi developers! Hi Dave!
>
> Testing RC1. Client is Win XP. Server is Debian Sarge.
>
> I have come across a peculiar effect while editing boolean fields. With
> other fields, if you want to discard your changes while editing a field,
> you hit <esc> and the original value is back (as long as you haven't
> saved yet). Not so with boolean fields. Pressing <esc> leaves yields
> seemingly random results.
> One of the most peculiar show cases:
> I click with the mouse. Value is TRUE.
> 1st click only sets the focus.
> 2nd click --> NULL
> 3rd click --> FALSE
> 4th click --> TRUE (again)
> If I hit <esc> now, I end up with FALSE (!). That wouldn't be by design,
> would it?

Probably not :-). I've committed a change which modifies the behaviour
such that simply clicking on the cell no longer cycles the value - it
now just displays the checkbox which must be explicitly clicked to
change the value. <ESC> now seems to do what is required, and I believe
this also has the side effect of curing the other inconsistency you
reported previously.

Thanks, Dave.


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

dpage@postgresql.org wrote:
> Erwin Brandstetter wrote:
>> (...)
>> If I hit <esc> now, I end up with FALSE (!). That wouldn't be by
>> design, would it?
>
> Probably not :-). I've committed a change which modifies the behaviour
> such that simply clicking on the cell no longer cycles the value - it
> now just displays the checkbox which must be explicitly clicked to
> change the value. <ESC> now seems to do what is required, and I
> believe this also has the side effect of curing the other
> inconsistency you reported previously.

I have checked out RC2 and the problem with <esc> seems to be gone. Nice!
About the previously reported issue: the mouse sticks to the regular
cycle (FALSE-TRUE-NULL) at all times, while <space> starts off
irregularly, before following the same sequence. This issue is not as
important IMO. It is, however, still there.

Regards
Erwin


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq