Compiled using C/Set++ ,WorkFrame 1.1, IBM's Toolkit 2.01 Csd's as of Nov 1994.
EPM is Registered to IBM Corp.
On Line help has been added to this version. If you are going to use the
programs in multiple working spaces as discribed later on the you may want
to change your HELP statement in config.sys. Otherwise for the time being client.hlp,
client.pro,client.prd and the have to be in the same working directory. OR you
may set The HELP enviornment variable in your CONFIG.SYS by adding
the directory to the HELP path statement. And copying client.hlp to the directory you
specify;
eg. SET HELP=C:\OS2;.........;MyDir:\...\directory_where_I_have_client.hlp;
The code is complete, however, somethings have been hidden, the theory of operation will be divulged to registered users only!
Installation is nothing more than copying client.exe to a working directory of your choice. Draging the program template from the templates folder to the Desktop or folder of your choice, and for starters set the filename to the fully qualified path and
for now, set the working directory to the sub-directory where you copied client.exe to. Copy client.pro and client.prd to the same working directory, later you will remove these two file (place in another working directory or delete altogether ). Make a
copy (allowing a new name to be generated ) of the program object you've just made and place a "s" in the paramater entry field in it settings notebook, this icon when double clicked will stop the timers in that enviornment space.
The program Client.exe generates two files when executed for the first time, "client.prd" and client.pro. Note: These two files will only be generated when the program is executed in the enviornment where the program client.exe resides. In other words.
Client.exe resides in Drive:\x\y executed from the os2 prompt [Drive:\x\y] type client.exe. , or in a settings notebook where the working directory entry field is blank. This is to keep from damaging possible pre-existing files. In the settings notebook
the working direct would be (drive:\x\y) . These files are data files containing the the Project (CLIENT ID) and the start and stop times of the respective projects (client timed events ). The two files may not be separated. They may be renamed for ar
chiving purposes. The program will not execute without both files in the same enviornment space ie. "working directory". The client.prd may be zero length (new) and execute thereby preserving the CLIENT ID's in the client profile (client.pro). The CLIE
NT ID's are system generated and are therefore transparent to the user. You may have multiple enviorments. Consider the following:
d:\client /* root dir */
d:\client\jan /* working space for january (environment) */
d:\client\feb
d:\client\...
d:\client\dec /* working space for december (envirnment )*/
d:\event1 /* working space of event1 and associated aspects to be timed */
d:\...\event2 /* event2 ditto */
WARNING ---YOU MUST HAVE A CLIENT.PRO CLIENT.PRD PAIR IN EACH ENVIORNMENT BEFORE THIS SCHEME WILL WORK. THIS MAY BE ACCOMPLISHED BY EXECUTING CLIENT.EXE IN EVERY WORKING DIRECTORY, YOU'LL NEED AS COPY OF CLIENT.EXE INT HE RESPECTIVE DIRECTORY, OR COPY THE
CLIENT.PRD,CLIENT.PRO PAIR BY DRAGGING AND DROPPING WHERE YOU WANT THEM.
Of course, If one wanted to one could have a client.exe file in every working directory but that wastes about 50k per working space.
Once the client header (pro) and data file (prd) exist in the enviornment the executable client.exe may be invoked from a particular enviornment by specifying the fully qualified path to the executable. You can have the same client.pro file in each envir
onment thereby keeping the same indexes and cleaning out the client.prd periodically by copying a new zero length client.prd file to the respective "working directory".
Assume for the moment client.exe is in the root. By having the template set in the 'program settings' for the Working Directory set to d:\client\june a profile is then created in sub-directory june these are a unique data pair although the client.prd and
client.prf are like names to other working directories. This method would and could be used to separated june events from July's events etc. This is also a way of keeping data file sizes small. Speed is not an issue memory requests howerver, are made by
file size. No attempt has been made to compress deleted data eg. the data is never actually deleted only references to the data and then only when the Marked for Deletion symbol (~) is present and Control|DeleteMarked is issued.
A third temporary (continually overwritten) file printfl.dat is used to store ASCII summary data. Its is reused each time a summary is created. Printfl.dat is viewed or edited via EPM.EXE so this OS2 applet must been in you path, if epm is not installed a
ny ascii editor may be used in the interim. Again it is created in the working enviornment. Tip: the CLIENT ID profile may be preserved by copying a newly created zero length client.prd file to the working directory. In this fashion the number of timed
events is unlimited.
The computer may be off! The program keeps track of the start and stop times to the nearest hundredth of an hour. In this aspect it is like as stopwatch.
In printfl.dat the starting time hack is kept using the d/m/y h:m:s and the elapsed time in hundreths of hours. A total is tallied for each project or event timed.
When the timer is stopped the ending time hacks are written only to the set enviornment space, thus stopping all timers in the working directory.
The summary ( printfl.dat ) data can be handled by EPM.EXE ( IBM Corp.) just like any plain text file.
Operation details:
Controls | NewProject; Enter up to 50 Characters then click ok.
( if here my mistake and you just want to start the timer click the start timer radio button and click ok ) WHENEVER a new enviornment (working directory is set) the program automatically opens at this dialog and prompts for a new client (project/e
vent) enter up to 50 characters and then click OK.
Controls|TimerControls; Project/events are in the upper list box currently timed projects/event are listed in the lower listbox. For currently untimed timed events in the upper listbox double clicking one or more listed item places them in the lower list
box or Currently timed list box. Timing starts when OK or DONE clicked. TIP: One could double-click an item in the upper list
box thereby placing it in the currently time list box, then highlighting the item in the lower list box click ok and nullify the operation. In order to STOP a timed event merely highlight the item in the lower list box.
Not currently time events upper box may be marked for deletion on a one at a time basis. The ~ tilde is placed before the event listing in the upper box. It is then not selectable. Check the Box Mark/UnMark for deletion. Double click the list box item a
nd the item is marked or unmarked with the tilde. TIP: If you mark an item for deletion the state of the varibles will not toggle, ie. you cannot toggle mark for deletion without first clicking ok or done. This does not mean you can only start or stop or
mark or unmark one thing at a time. ( One could start five timers, stop two timers, mark several for deletion (only if not running), unmark several and then press Ok or Done.
Controls | Delete Marked.
This deletes forever the reference to that event. It's gone, it's deleted, it's lost! Please note items that are marked for deletion are item that can not be selected for starting the timer. Note: They may be unmarked for deletion and started by first
checking the mark/unmark box then clicking ok and then started via the Time Controls dialog box!
Controls | Project Summary :
Here data is summarized, and over written to environment\printdf.dat. TIP: Data events/projects that have been marked for deletion may still be summarized.
Controls | View Project Summary : Here EPM.exe must be in your path.
If it is not you will have to handle the file drive:\...\...\printfl.dat using your favorite editor. Where \...\... are the set workiing directory /environment.
All timers may be shutdown via a command line call eg, CLIENT <s|S>top. If more than one enviornment is being used, the fully qualified path is necessary !
Limitations: Only one new client/project/event may be added at a time all cycles are completed with the OK. This could be tedious therefore one can copy the master client.pro to another enviornment once the program has initiated a client.pro, client.prd
pair.
In other words, new scenarios may be initiated with multiple copies of client.pro in unique working directories more details about this feature and other capabalities will be made available to registered users. Please this is not freeware. CIS users reg
istration is via GO SWREG it's easy.
Fixes:
Fixed improper handling of dialog boxes closing. (FCF_SYSMENU). (By elimination!)
