Daisy Analysis Daisy Status

The Daisy Status started as a test program written to provide an 'external' Debug.Print for the debugging of Visual Basic, both during testing and after compiling the executable.


An Example

Trace for Editing Browser

Shown is a trace produced of a series of 'status messages' produced by the Daisy 2003 Editing Browser.

This was the program for which Daisy Status was first written, in an attempt to solve a rather knotty and difficult bug during development.

This product will be released in the near future and the 'trace' has been left in the program, despite the fact, it was only originally added during testing.


Features

The features of Daisy Status have grown as it soon became apparent that the program had other uses, than just being a more user-friendly replacement for Debug.Print in Visual Basic :-

  1. As Daisy Status is fully ActiveX compliant it can be called by any program that is capable of controlling another using this technology.

  2. The main status window of Daisy Status can also be made to float on top of all other windows if required.

  3. The window can be cleared under program control, thus every time your program runs it can create a new set of messages.

  4. The contents of the window can be loaded and read under program control.

  5. Position, size, icon and caption of Daisy Status can also be set under program control.


Programs, Source Code and Testing

Full source code is included in the download for the program.

Download Daisy 2003 Status!

This also includes the full source of a test program.

The program is installed in the normal way.


Programming

Start by looking at the Daisy 2003 Status Test project that is stored in the file, Daisy2003StatusTest.dyp. By default, this will be stored in the SourceFiles sub-directory of where you installed the program.

Open up the References using the Project menu.

Daisy 2003 Status Test - References

Note the reference to Daisy 2003 Status X, which is the ActiveX program, Daisy2003Status.exe, which mechanises the status window.

Look at the two source files that make up the program.

In most new programs just add the Daisy2003StatusTestSubs.bas file and make the appropriate calls. Note that StatusObject is used to hold an object that contains a copy of Daisy 2003 Status.

Look at frmDaisy2003StatusTest.frm in the test program to see the various calls :-

  1. Start the status window in the Form_Load using the subroutine, StartStatusProgram

  2. Close the status window if you need to in the Form_Unload using CloseStatusProgram.

  3. Each message is added to the status window using DaisyStatusMessage.

  4. Note that calls are also used to clear the status window and return its contents.

Feel free to change and modify the code in any way you want.


Copyright 1999-2003 by James Miller of Daisy Analysis Ltd.