Chapter 10 Using VFP's Object- Oriented Tools - dFPUG-Portal

More documents

Recommendations

Info

286 The Fundamentals of Visual FoxPro 6.0 Control Property/Method Description Forms (continued) Load() Destroy() See Listing 10.1 at the end of this table. *Hide the form so it *appears to go away *faster. This.Hide() Labels AutoSize = .T. BackStyle = Transparent Caption = “lbl” Command Caption = “cmd” Buttons Page Frames ActivePage = 0 PageCount = 0 All datarelated controls—text boxes, check boxes, combos, lists, etc. Text and Edit Boxes TabStyle = Nonjustified AnyChange (custom method) Add the following code to the InterActiveChange and ProgrammaticChange events: This.AnyChange() Why? So you can centralize code that should be called if either the InterActiveChange event or the ProgrammaticChange event is called. You can still put code that is specific to either InterActiveChange or ProgrammaticChange in the respective method, but this technique saves a lot of redundant code. Valid() See Listing 10.2 at the end of this table. Validation (custom method) This method is called from the Valid() method. IntegralHeight = .T. SelectOnEntry = .T. Valid() Check Boxes AutoSize = .T. BackStyle = Transparent Caption = “chk” Valid() Option Groups OptionGroup AutoSize = .T. BackStyle = Transparent ButtonCount = 12 Valid() Option groups have buttons that are not already subclassed and can’t be subclassed. So ignore the Option Button class. I create an Option group with a dozen option buttons that are already preconfigured. Then I set Enabled and Visible to False and resize the option group. That way, the buttons have the properties already. Option button properties: AutoSize = .T. Caption = “1” through “12” List Boxes IntegralHeight = .T. List boxes don’t get a Valid() because the Valid() fires each time you move the highlight in the list box.
Section II Chapter 10: Using VFP’s Object-Oriented Tools 287 Control Property/Method Description List and Combo Boxes aItems[1] (custom property) RowSourceType = 5 - Array RowSource = this.aItems ItemTips = .T. SelectOnEntry = .T. Init() This.aItems[1] = “” Spinners SelectOnEntry = .T. Grids AllowHeaderSizing = .F. AllowRowSizing = .F. DeleteMark = .F. RecordMark = .F. SplitBar = .F. Enter “aItems[1]” in the property name so that Visual FoxPro knows it’s an array. You might want to turn ItemTips to True, so that the entire row is displayed when the combo is opened. You might want to turn SelectOnEntry to True so that an item in the combo is automatically selected when the user tabs into the control. Listing 10.1. The Form controls’ Load() method code from the above table. * Set some environmental things the way we want. set talk off if oApp.lCentIsOn set century on else set century off endif set deleted on if upper(oApp.cMethod) = "DEV" set escape on else set escape off endif set exact off set exclusive off set fullpath on set near off set safety off if oApp.cMethod = "DEV" set strictdate to 2 else set strictdate to 1 endif set unique off Listing 10.2. The data-related controls’ Valid() method code from the above table. *\\\ except list boxes *\\\ compliments of Doug Hennig * If the Valid method is fired because the user clicked on a button * with the Cancel property set to .T. or if the button has an lCancel * property (which is part of the SFCommandButton base class) and it's * .T., don't bother doing the rest of the validation.
Page 1 and 2: Section II Chapter 10: Using VFP’
Page 29: Section II Chapter 10: Using VFP’
Page 35: Section II Chapter 10: Using VFP’

Chapter 10 Using VFP's Object- Oriented Tools - dFPUG-Portal

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?