Mike, I like the fact that the Speed Button in not in the tab sequence and wouldn't like to lose that. I also like the alternative for the PushButton being in the tab sequence That way the user has the choice.
However, as with almost anything, if there is _different_ behaviour in similar controls then confusion, if not errors, will result. In this case, my guess is that most people would _expect_ the field that the cursor is in to be updated with either button. It may be clear that a difference _should_ be expected but I doubt many would think to check first. It then follows that _if_ a difference is intended then the documentation should clearly indicate it. Conversely, if they are meant to work interchangeably - apart from the obvious differences of display and tab sequence, then the same results should be obtained. Regards, Alastair. ----- Original Message ----- From: "MikeB" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, November 22, 2004 7:43 PM Subject: [RBG7-L] - Speed/Enhanced Speed Buttons vs Pushbutton > The question is whether the following behavior is expected or acceptable. > > Put a variable edit or memo on a form. > > Place two buttons on the form. 1 of each type of (enhanced or standard) Speed > button and a Pushbutton. > > In the OnClick eep of each button put the following code > > Pause 2 using .vTheVariableAssignedToTheEditControl > return > > What happens is the standard pushbutton will display the value of whatever you > type in the Edit Control, but the Speed button will have null assigned to the > variable (unless you click the pushbutton one first which takes Focus) and the > pause will be empty. > > Because the (Enhanced or Standard) Speed button can't receive Focus (It doesn't > take a TabStop), the focus never leaves the Edit Box and the underlying > Variable does not get updated to the Text Value displayed. > > So, Is this the behavior that is expected? > I don't know. > > Desirable? No. My judgment is stilted because I fussed with it for a couple of > hours before I figured it was the Speed Button that was keeping the variable > assigned to the control from being updated :-( > > Can I Live with it? > Yes, but would still like it if the Enhanced buttons would work like the > Pushbutton. > > An acceptable workaround would be if the underlying TEXTVALUE of the Variable > Edit/Variable Memo/Variable RichEdit(when used in variable mode, not filemode) > would be accessible regardless of focus, meaning anytime you called GetProperty > <componentID> TEXTVALUE 'vVarToReceiveTheValue' , whatever was displayed in the > Variable Edit control would be updated to the underlying TEXTVALUE and Variable > assigned to the Control(if ANY)... > > This is far from a Show Stopper as I can deal with it using the Pushbutton, but > I would like to see (a few) Comments.. > > Mike >
