Printing - FoxTalk - dFPUG-Portal

More documents

Recommendations

Info

SCX, should you need to subclass the functionality of a form. Since an individual class library can contain any number of classes, and the Class Designer can edit only one class at a time, the menu and command line interfaces to access the Class Designer are clumsy. It's much easier to navigate a class hierarchy in the Class Browser and invoke the Class Designer for the class you've selected in the Browser. The Class Designer allows developers to create classes visually. These classes can be either visual or non-visual (Custom) subclasses. Custom properties and methods can be added to a class and will appear in the Properties window for visual editing. The Form Designer allows forms to be created by subclassing existing classes by dropping them onto the form surface from the Controls toolbar. The object model in Visual FoxPro supports container classes. Container classes are classes that can contain objects as members. For example, Forms and FormSets in an SCX are containers. The FormSet can contain Form objects, while the Form can contain control and Custom objects, as well as other containers such as OptionGroups and CommandGroups. The Toolbar class is a container that can contain control objects. Control classes such as the CommandButton class aren't container classes since they can't contain objects. If you experiment with the Save As Class dialog box in the Form Designer, you'll notice that you can save controls as classes into a .VCX . You can also select multiple controls and save all selected controls. You can even save an entire form (including its object members) as a single class. When you select an individual control (or just the form) and you save the selected (single) object as a class, you are creating a class based on the object's classification. When you save a group of selected controls or the entire form that contains controls into a single class, you are actually saving a container class. A Wild Ride, But Worth It Bob Grommes I've been editor of FoxTalk now for two and a half years. During my watch, FoxTalk has grown from 24 to 32 pages, we've redesigned the visuals, added many new features, and covered the release of FoxPro 2.6 and Visual FoxPro. Two and a half years ago we still struggled with 286 client machines; now we fret about those slow 386 machines and how to shoehorn applications into 8M of RAM. Less than a year ago, we passed arguments to functions, and now we send messages to methods. As the saying goes, "the only constant in this business is change." But what really defines the essence of an experience are the people -- subscribers and the staff at Pinnacle alike. My experience as editor has been a richly rewarding time of service to the FoxPro community. I've made a lot of friends, had a lot of fun, and grown tremendously. So it's with many warm memories like these, and with more than a little regret, that I've decided to leave my post as editor to concentrate on other projects, including a Visual FoxPro book planned for late 1996. It was a difficult decision. Thank you for your letters, suggestions, and
constructive criticisms. I treasure them all. The loyalty of FoxTalk subscribers is something to behold. You really care about this publication! I hope you'll be as kind to my successor, Whil Hentzen . Whil needs little introduction: he's been a regular columnist in FoxTalk since before my time, has served the past few months on our Editorial Advisory Board, and is probably one of the best-connected and best-liked folks in the Fox community. He's president of Hentzenwerke Inc. in Milwaukee, Wisconsin, a FoxPro development firm that each November sponsors the Great Lakes Great Database Workshop for FoxPro developers. In addition, Whil is a driving force behind the FoxPro user group in his area, as well as the author of the new book Programming Visual FoxPro 3.0 from Ziff-Davis. Somehow, he finds the time to run competitively and raise three children with his wife, Linda. I hope that you'll take a moment to extend Whil a warm welcome (he can be reached on CompuServe 70651,2270). I won't be disappearing entirely from these pages; indeed, I may have more time to write articles than I did as editor! I wish you and yours the best of success in the coming years, and invite you to keep in touch (I can still be reached on CompuServe 74126,72). Tip: Set Focus to a Control When a Record is Added William O'Connor To set focus to a particular control when a record is added, add a new property to your form called cAddfield. Then add this method and give it the name of your choice: * This method requires the form to have a property * called cAddField. cAddField MUST contain a fully * specified object path pointing to the object. * For example: * cAddField = 'PageFrame1.Page1.txtEmployee' * Please note that this will set focus, but won't change * the page to show the field if it is on the non-current * page of a pageframe. IF TYPE("THISFORM.cAddField") = "C" AND ; NOT EMPTY(THISFORM.cAddField) cObjName = ALLTRIM(ThisForm.cAddField) = EVALUATE("THISFORM." + ALLTRIM(cObjName) ; + ".SetFocus()") ENDIF
Page 1 and 2: January 1996 Extend the Visual FoxP
Page 3 and 4: Passing the name of a registered ad
Page 5 and 6: Sometimes an add-in most appropriat
Page 7: Summary As you can see, the Class B
Page 11 and 12: "come back out." The button on the
Page 13 and 14: Black portion of .MSK file White Th
Page 15 and 16: TextBox objects on every form you c
Page 17 and 18: ings up a pop-up menu. Choose the A
Page 19 and 20: usiness rules because they aren't b
Page 21 and 22: 3. In the Command window, enter o=S
Page 23 and 24: on a page frame, you'll need a subc
Page 25 and 26: created, however, you must use only
Page 27 and 28: a record in the .SCX. Two fields in
Page 29 and 30: A Glossary of Object-Oriented Termi
Page 31 and 32: Encapsulation Ecapsulation is the c
Page 33 and 34: Memo fields (variable-length fields
Page 35 and 36: (VCXs), regardless of what you curr
Page 37 and 38: do a single REPLACE: cNewMessages =
Page 39 and 40: change the superclass method, those
Page 41 and 42: Tabbed interfaces, such as those im
Page 43 and 44: * Initialize the variable for the c
Page 45 and 46: The first key to making everything
Page 47 and 48: when the button is disabled. The Sc
Page 49 and 50: *:SPRDRV6 NO_READ Here's the GENSCR
Page 51: Fox World News Micromega Systems ha

Printing - FoxTalk - dFPUG-Portal

Create successful ePaper yourself

Delete template?

Save as template?