EditMultiSelectClass Functional Organization - Expected Use


Top  Previous  Next

As an aid to understanding the EditMultiSelectClass 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 EditMultiSelectClass 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 (v)

initialize the EditMultiSelectClass object

 

AddValue

prime the MultiSelect dialog

 

Kill (v)

shut down the EditMultiSelectClass object

Mainstream Use:

 

TakeAction (v)

handle user actions for the dialog

 

TakeEvent (v)

handle events for the edit control

Occasional Use:

 

CreateContol (v)

create the edit (COMBO) control

 

Reset

clear the MultiSelect dialog

 

SetAlerts (vi)

alert keystrokes for the edit 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

initialize the EditMultiSelectClass object

 

CreateContol

create the edit (COMBO) control

 

DeserializeValue

extract values from EIP column to selected queue

 

SetAlerts (i)

alert keystrokes for the edit control

 

SerializeValue

process selected items to EIP column

 

TakeAction

handle user actions for the dialog

 

TakeCompletedInit

pre-process serialized values

 

TakeCompletedProcess

post-process of serialized values

 

TakeEvent

handle events for the edit control

 

Kill

shut down the EditMultiSelectClass object