EditCheckClass Functional Organization Expected Use

Top  Previous  Next

As an aid to understanding the EditCheckClass it is useful to organize its methods into two large categories according to their expected use—the primary interface and the virtual methods. This organization reflects what we believe is typical use of the EditCheckClass methods.

Non-Virtual Methods

The Non-Virtual Methods, which you are likely to call fairly routinely from your program, can be further divided into three categories:

Housekeeping (one-time) Use:

 

Init (vi)

initialize the EditCheckClass object

 

Kill (vi)

shut down the EditCheckClass object

Mainstream Use:

 

TakeEvent (vi)

handle events for the CHECK control

Occasional Use:

 

CreateContol (v)

create the CHECK control

 

SetAlerts (vi)

alert keystrokes for the CHECK control

(v) These methods are also virtual.

(i) These methods are inherited from the EditClass

Virtual Methods

Typically you will not call these methods directly—the Non-Virtual Methods call them. However, we anticipate you will often want to override these methods, and because they are virtual, they are very easy to override. These methods do provide reasonable default behavior in case you do not want to override them.

 

Init(i)

initialize the EditCheckClass object

 

CreateContol

create the CHECK control

 

SetAlerts(i)

alert keystrokes for the CHECK control

 

TakeEvent(i)

handle events for the CHECK control

 

Kill(i)

shut down the EditCheckClass object