I agree with you MIke. I second requesting this change David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: "MikeB" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, November 22, 2004 4:19 PM Subject: [RBG7-L] - Re: Speed/Enhanced Speed Buttons vs Pushbutton
> > ----- Original Message ----- > From: "David M. Blocker" <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> > Sent: Monday, November 22, 2004 3:47 PM > Subject: [RBG7-L] - Re: Speed/Enhanced Speed Buttons vs Pushbutton > > > > Mike > > > > I ran into this in the past as well and replaced my Speed buttons with Push > > Buttons or Bit Buttons > > > > I was told at the time that it was correct behavior for a Speed Button > > Javier's workaround will overcome the issue OK. > > I Like the speed buttons, but still think there should be a way to get at any > variables value in an EEP. Skip 1 forces the variable update, so it is just a > question of whether the Delphi/Rbase code should be added to the Speed button > by default. > > I'm Ok with the workaround as it is trivial, but would like to see at some > point that when the GetProperty <componentID> TEXTVALUE 'vValue' command is > issued against any edit box, whether it is a variable edit or whatever, the > TEXTVALUE is returned, then the point would be moot whether the Focus has any > effect on the variable update or not. > > > > > > David Blocker > > [EMAIL PROTECTED] > > 781-784-1919 > > Fax: 781-784-1860 > > Cell: 339-206-0261 > > ----- Original Message ----- > > From: "MikeB" <[EMAIL PROTECTED]> > > To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> > > Sent: Monday, November 22, 2004 2: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 > > > > > > > > >
