Yes I am in agreement with the speed buttons purpose is to not include a Tab Stop.
I just want you to opine on whether a variable you would want to process within the context of the Speed Button EEP should have access to the actual data that is displayed on the screen at the time of execution. I didn't Try Skip 1 till now, but that would work OK as a workaround..Even when there is no other control to skip to... ----- Original Message ----- From: "Javier Valencia" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, November 22, 2004 3:33 PM Subject: [RBG7-L] - RE: Speed/Enhanced Speed Buttons vs Pushbutton > Mike, Sami: > I just run a quick test just to verify that my impression of what the > buttons did was correct. IMHO, the speed button works as it should, as it > does not include a tab stop it should not update that field...technically it > never quite leaves the field; in fact, after you exit the speed button, you > will notice that the cursor is in the exact place where it was when the > speed button was pressed (try placing the cursor in the middle of the > variable and press the speed button). A simple workaround is to use the > command: SKIP 1 at the beginning of the EEP to force an exit from the field > and thus display the correct value. Maybe the buttons need to be updated so > they can all look the same. > I use mostly speed buttons, as I do not like them to be accessible through > tab stops. It would be helpful to have a quick description (there is > probably one in FTE) of what are the actual differences between the buttons > (bit, speed, office, shape) other than tab stops...maybe all we need is 2 > types of buttons one that is accessible though tab stops and one that is > not, with both types having all the cosmetic bells and whistles... > Javier, > > Javier Valencia, PE > President > Valencia Technology Group, L.L.C. > 14315 S. Twilight Ln, Suite #14 > Olathe, Kansas 66062-4578 > Office (913)829-0888 > Fax (913)649-2904 > Cell (913)915-3137 > ================================================ > Attention: > The information contained in this message and or attachments is intended > only for the person or entity to which it is addressed and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended recipient > is prohibited. If you received this in error, please contact the sender and > delete the material from all system and destroy all copies. > ====================================================== > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sami Aaron > Sent: Monday, November 22, 2004 2:12 PM > To: RBG7-L Mailing List > Subject: [RBG7-L] - RE: Speed/Enhanced Speed Buttons vs Pushbutton > > Mike - > > This addresses a question I received from another developer in just that > last day or so - my initial response to him was to use one of the buttons > that included the tab stop - but he didn't like the look of those as well. > So from a consistency standpoint it's a little confusing and somewhat > limiting. > > On the other hand, I like the idea of having buttons available that DO NOT > have a tab stop... > > On the third hand, I'd like an Exit EEP on the variable field to execute > whenever the user clicked on any kind of button or other object on the > form - and that's not happening now if the user clicks on an object that > does not include a tab stop. > > I guess I'd like to have three hands ... > > Sami > > ------------------------------------------ > Sami Aaron > Software Management Specialists > 19312 W 63rd Terr > Shawnee KS 66218 > 913-915-1971 > mailto:[EMAIL PROTECTED] > www.softwaremgmt.com > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of MikeB > > Sent: Monday, November 22, 2004 1:43 PM > > To: RBG7-L Mailing List > > 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 > > > > >
