When editing a non-null field in the contents table of
the object tree, if one attempts to remove the last
character of the current value, nothing appears to
happen. It appears that the backspace key event is
being swallowed. In fact, what is actually happening is
the KeyTextHandler is misinterpreting the text as that
which was already there. However, the text is the new
value and since the new value has length 0, it is never
allowed to become the value in the cell. Obviously, it
isn't a valid value, but the comment in the code
indicates - and rightly so - that the user must be
allowed to clear the contents of the cell. As it is
right now, that it not happening, so the code isn't
doing what it was intended to do. It's very annoying to
have to place type the new value without clearing the
original value, just so you can clear the original
value. I have a fix for this issue that I'm currently
testing. The new behavior will still cycle to the
original value when the user hits backspace after the
cell has already been cleared.
Rob
Logged In: YES
user_id=1287991
This is fixed in CVS.