Changes since version 0.90: =========================== * Added the /Q commandline option to terminate PM Timer from the commandline so the user won't have to shut down PM Timer himself when the program is run from a batchfile. * Added the /H commandline option to start PM Timer invisible. * PM Timer now also displays the online time in the titlebar of the active window. Now the online time will always be visible for the user, even if the PM Timer window is covered or hidden. * Moved the settings to a notebook. Working on 'international' settings, so not only Dutch people but everybody can use PM Timer. * Added a check for screen resolution. PM Timer will automagically detect if your screen resolution has changed since the last run. If it has, it will not use it's saved window sizes and positions. Changes since version 0.95: (not released!) =========================== * Added 'flyover' help to the settings notebook. * Added an option "Use OS2.INI" to the general settings page. If checked, the program will save it's main- and logwindow apearance in OS2.INI. This means that drag 'n dropped colors and fonts will also be saved. If the button is not checked, PM Timer uses it's own private ini-file and only saves window positions. NOTE: Ones checked, an entry for PM Timer will be created in OS2.INI. Space occupied is approx. 500 bytes. If you afterwards decide that you don't need this feature, the entry in PM Timer will still be there! Well, if you know what I'm talking about you'll also know how you can remove the entry with a decent ini-file editor. I haven't bothered to write some code just to remove 500 bytes from OS2.INI. Other programs (that you pay for) have much larger entries and still don't have options to remove them. Why all this trouble to decide to use OS2.INI or not? Well, personally I don't like the idea of all programs using the same ini-file (my os2.ini is 1.8Mb at the moment, sick..). On the other hand OS/2 doesn't provide an API to save all presentation parameters (colors, fonts etc.) of a window to a private ini. So that's the reason for providing you with a choice. If you don't like the program's default colors, you can change them using drag and drop, but they'll only be saved if you allow the program to use os2.ini. Don't know why I'm telling you all this.. Just wanted you to know, I guess :) * Added an option to the General settings notebookpage to specifiy a maximum size for the logfile. If the logfile grows beyond this value the program will start deleting the oldest log-entries. Don't set the value to small though. PM Timer needs the logfile entries to calculate your phonecosts. I have it set to 65kB and that keeps a log for approx. four months back (depends on how much you call ofcourse) which is sufficient for me. * Polished the titlebar display of the timer a little: No more tampering with the original titlebar text and added some colors. * Added an option to the General settings notebookpage to specify the number of additional third party buttons on the right side of the titlebar. Without the option, the timer titlebar display would be covered by the additional buttons. Changes since version 1.00: =========================== * Added an option to let PM Timer beep a certain amount of time before the next time interval (i.e. when the costs are increased) begins. This way you can make optimum use of your online time. You can specify the number of seconds before the next time interval that PM Timer should warn you on the general settings notebook page. * Fixed serious bug in com-port setting. PMTimer internaly switched the addresses of Com 1 and Com 4. So if you selected Com 1 as the port to be monitored in the settings, PM Timer would actually monitor Com 4. * PM Timer tried displaying its titlebar timer on the launchpad even when the launchpad's frame controls were disabled. Fixed that. * Added more flexibility to the port monitoring capabilities of PM Timer. Now you can select between monitoring by means of direct port access (IOPL), by driver access (COM.SYS/SIO.SYS) or not monitoring the port at all. If you choose the direct port access option, you'll also be able to enter a different base address for the serial port PM Timer should watch in case your port isn't on the standard comport address. The recommended way to monitor the port is by using *direct* port access. This produces the least overhead but more import, some communications programs (Dial Other Internet Providers from the IAK is an example) don't drop the Carrier signal when you tell it to hang up if PM Timer uses the serial driver to monitor the ports. Thus the modem stays online and you have to 'hang up' by hand. Another problem using driver access are DOS communication programs. Dos sessions really don't like sharing the communictions driver with other apps. * Added support for the new Warp 4 notebook style. * Changed the number of costs/time fields in the costs settings from 4 to 8. For some countries (e.g. Germany) the 4 fields wasn't enough. For the same reason the Local/Long distance meganism has been extended to 4 different distance zones. You now have Local (zone 0), Zone 1, Zone 2 and Zone 3. * Commandline syntax has been extended to support the new zones. /Zx (where x = 0,1,2 or 3) sets the zone on startup. /Z0 will have the same effect as /L (select Local call) * Also added /W commandline parameter. If specified, PM Timer will *not* display the Warning dialog upon program exit while it's still timing. I only recommend its use if you run PM Timer *unattended* from a batchfile. Changes since version 1.10: =========================== * Added the current costs to the titlebar display while online. Changes since version 1.11: =========================== * Fixed a rounding bug in the calculation dialog. Thanks to Jaap for reporting this one. * Fixed up the helptexts in the settings notebook a little bit. * PMT has it's own logo now. Changes since version 1.11a: ============================