21
edits
Changes
m
→Public Methods
<hr/>
====Public Methods====
=====Add methods=====
the '''IO_Form''' must be able to add the IO_Field classes to itself one at a time and then provide the user, the means of editing them in order they were added.
'''IO_Form''' uses this private add method to provide means of adding fields through several public add methods. this method adds an IO_Field to the end of the IO_Fields in the IO_Form;
<big><pre>
int add(IO_Field* f, bool dynamic, bool submitter);
</pre></big>
'''f''': is the address of the IO_Field begin added to the IO_Form
'''dynamic''': if set to true, it sets this IO_Field to be deallocated by IO_Form's
destructor at the end;
<blockquote>
note: each IO_Field in IO_Form should have a flag, corresponding to the way
it was added to it. If this flag '''"dynamic"''' is set to '''true''', then
it means that the added IO_Field was created dynamically and it is the
responsibility of the IO_Form's destructor to deallocate the IO_Field at
the end. How ever if '''dynamic''' flag is set to false, the IO_Form's
destructor will not deallocate this IO_Field from memory when IO_Form goes
out of scope.
</blockquote>
'''submitter''': if set to true, it sets this IO_Field to terminate the IO_Form's
edit if ENTER_KEY is hit. see the edit() method for more info.
<blockquote>
note: like dynamic flags corresponding to IO_Fields, there should be also
submitter flags corresponding to each IO_Field in the IO_Form to be able
to tag some of the IO_Fields to terminate the edit function if needed.
(ie. Cancel or Submit a form using a Field)
</blockquote>
--- incomplete ----
