Release 10.1A: OpenEdge Development:
AppBuilder

> ## SmartObject properties

> A SmartObject has few editable properties of its own, although the basic objects that make up its run-time representation, if any, have all the properties associated with their kind. There is no Advanced Properties dialog box for a SmartObject as such, though there is for any widget the object uses for its run-time representation.

> You can open the Property Sheet for a SmartObject other than a SmartWindow, SmartDialog, or SmartFrame by any of these methods:

> - Clicking its menu button and selecting the Properties menu item.

> - Right-clicking on the object and selecting the Properties menu item.

> - Selecting the object and choosing Tools Property Sheet.

> The Property Sheet dialog box then opens:

> This Property Sheet dialog box combines information about both the master object and the particular selected instance. The fields are:

> - Instance handle identifier — You should change this to more clearly reflect the role of the object in your application.

> - Object type identifier — This is always a read-only field; it merely identifies the class to which this object belongs.

> - Filename of the master — Choosing the File pushbutton opens a dialog box that allows you to associate a different master with this instance. Be cautious about using this ability.

> - List of instance properties — The nature of the properties varies with the object class. See the relevant chapter of this manual for a description of the instance properties pertaining to a particular SmartObject class. Choose the Edit button to change the editable properties.

> - Parameterize as variable check box — Normally cleared. Setting this box causes AppBuilder to treat this object as a placeholder for its class rather than as an instance of a specific master object.

> By default, every instance of a SmartObject represents a particular master object with a defined set of behaviors. For example, a given SmartDataBrowser instance is constrained to display a certain set of fields, generally from a particular database, and only those fields. Under some circumstances, you might find it advantageous to be able to treat a SmartObject instance as a design-time placeholder, instead. That would allow you to defer the choice of master until run time, when you could choose, load, and run a situation-specific instance under program control. See the "Creating a SmartObject placeholder" section for information about how to do this.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095