Clarion Community Help

| **Navigation:**  [[abc library reference.htm|ABC Library Reference]] > EditFileClass > EditFileClass Methods >====== EditFileClass Functional Organization - Expected Use{{c6h0009.jpg|C6H0009.jpg}} ====== | [[editfileclass methods.htm|{{btn_prev_n.gif|Previous page}}]][[abc library reference.htm|{{btn_home_n.gif|Return to chapter overview}}]][[createcontrol  create the edit in place control editfileclass .htm|{{btn_next_n.gif|Next page}}]] |
|  ||

As an aid to understanding the EditFileClass 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 EditFileClass 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 EditFileClass object |
|  | Kill (vi) | shut down the EditFileClass object |

**Mainstream Use:**

|  | TakeEvent (vi) | handle events for the edit control |

**Occasional Use:**

|  | CreateContol (v) | create the edit (COMBO) control |
|  | 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 (i) | initialize the EditFileClass object |
|  | CreateContol | create the edit (COMBO) control |
|  | SetAlerts (i) | alert keystrokes for the edit control |
|  | TakeEvent (i) | handle events for the edit control |
|  | Kill (i) | shut down the EditFileClass object |