Class TfrmSocket (unit Unit1) |
TStandardForm
****************************************************************** Inherited off of STDFORM. This is the parent for all other inherited CBN Standard Forms. ********************************************************************* 03/27/97 JMPERR Initial.
Constructors |
Functions |
****************************************************************** Override the SetMessage method that writes the message to the status bar.
Properties |
Events |
Variables |
Constructors |
Functions |
Place visual GUI setup code here. {case state of fsShow: begin end; fsBrowse: begin end; fsInsert: begin end; fsEdit: begin end; end;} ...etc
procedure SetMessage(msg : String); override;
****************************************************************** Override the SetMessage method that writes the message to the status bar. Generally, you won't ever use this. ********************************************************************* 03/27/97 JMPERR Initial. ********************************************************************} {procedure TfrmStandardForm.SetMessage(msg : String); begin // inherited; // Override "msg.mbar" SetMessage behavior. end;} {******************************************************************** ALL code for the setup of the screen's GUI, even based on the business rules of the system. Only in rare cases would you place GUI control code elsewhere, not even form Activate. The currently declared states are: type TFormState = (fsBrowse, fsEdit, fsInsert, fsInactive, fsRowChange, fsShow, fsOption1, fsOption2, fsOption3, fsOption4, fsOption5, fsOption6, fsOption7, fsOption8, fsOption9, fsOption10, fsOption11, fsOption12, fsOption13, fsOption14, fsOption15); In order to user the optionals, declare them as a constant, at the top of the form, and then you can use them. ********************************************************************* 03/27/97 JMPERR Initial.
Properties |
Events |
Variables |