Frank,
I think this might be a perception problem. Here is the orinigal poster's description of the problem:
I have a problem when using "@K" picture clause. If I have several controls on a window or dialog and the user tabs or presses enter to move through the controls the get text is correctly deleted if they user types a character in a get. However, if the user clicks on a control using the mouse and types a character the text of the get is not deleted and the character typed is simply inserted (or overwrites) the text in the control.
Can someone confirm (or not) this problem?
Clipper Help for @K picture:
Deletes default text if first key is not a cursor key
xHarbour help:
Allows a suggested value to be seen within the GET
area but clears it if any non-cusor key is pressed when
the cursor is in the first Position in the GET area.
Note that with Clipper you cannot click into a field, so the only way to get there is to use the Enter key. So, with Clipper you cannot enter the field in any position other than the first position.
Note also that the xHarbour help file specifically states that it clears the Get if "the cursor in in the
first position in the Get area." The original poster assumed that the Get should be cleared if any non-cursor key was typed after clicking into the Get in
any position. Perhaps this behavior is
desirable, but it is not the way Clipper's Gets worked and thus is not the way xHarbour's Gets work (by design). [Remember that FWH's TGet class contains a xHarbour (or Harbour) Get object.]
So, the current behavior is not a bug, it is true to Clipper's Get's behavior. The question becomes should this behavior be changed, or at least optional, in the Windows environment. I don't know if it would be possible to get a consensus on doing this to the xHarbour/Harbour Get class since they like to remain true to Clipper. And, I don't know if this can be done in the FWH TGet class.
Regards,
James