OK! It is a bad pun and probably only works in English.

For those users that like to track weight, I've now added support for for this in version 1.3.0 which you can get here: this has been mainly requested by Type II sufferers and I hope it helps.

As for height: this is tracked at my son's clinic, so I suspect it may be useful for younger diabetes sufferers. If nothing else it is useful to keep a record of this for when going to a theme park which has height restrictions on some rides

These new reports are part of the Graph report option. However, each report is only generated if there are any events that record the associated data. I decided it is better to not to show a blank graph as I suspect many users will not want to track this data.

The database is saved within the application's preferences file com.Nesfield.DiabetesLogbookX.plist which is stored in the user's Preferences folder of their Library. It is strongly recommended that this file is regularly backed up: preferably to a volume that is not the same as the one on which your account data is stored; suitable backup volumes would be iDisk, a networked folder, another computer, or to CD or DVD.

To restore the backed up file, without the application running, simple copy the file back into the Preferences folder then restart the application.

We use the OneTouch UltraSmart, plus a couple of Ultras. There are two programs that support upload, at least for the OneTouch meters: HealthEngage Diabetes and The Body Journal. I tried both many times, especially after we got the UltraSmart. The Body Journal is a general medical program and it only downloads the glucose events from the meter. HealthEngage Diabetes downloads all events (if I recall) from the meter. But, for us, the reports didn't meet our needs.

I did try using the OneTouch software within a virtual PC on our Mac: it worked well, but again the reports weren't what we wanted - and there was so much white space I couldn't bring myself to use that much paper.

My wife now only uses the UltraSmart for glucose, with insulin events added when we are away from home. As for adding meter support, I'm not that smart, just a Dad trying to help my boy. I'd love to support meters, but it might not happen.

I was recently contacted by a pump user about how to use Diabetes Logbook X. After a few emails we arrived at this method:

[I'm guided by the pump user as I have no experience with them at all.]

1. For reference, record the pump pattern settings (A, B, and Standard) for the various times of day and insulin units. This can be achieved in a number of ways such as:
   
   • 
     
   • In Notes-only events in the logbook, which then gets displayed in the Notes report. [A Notes-only event only uses the event name, notes and flag fields.]
     
     
   • Create a new iCal calendar for use with the logbook. Then create diary entries/tasks/notes with the pump information. [Use the iCal item in Diabetes Logbook X's Window menu to easily access iCal.]
   
   
2. Setup Diabetes Logbook X insulins:
   
   • 
     
   • Within the logbook User Settings, edit the insulins list and add two entries such as: Basal; Bolus.
     
     
   • Within the logbook User Settings, edit the medicines list and add three entries such as: A; B; Standard.
     
     
   • Within the logbook User Settings, pre-set Insulin A to Bolus, Insulin B to Basal, and Medicine to the appropriate pump pattern (A/B/Standard).
   
   
3. Create events in the logbook:
   
   • 
     
   • Use Insulin A field to record bolus insulin units.
     
     
   • Use Insulin B field to record the basal insulin units.
     
     
   • Use Medicine field to record the pump pattern used for the day.
     
     
   • When recording pumped basal insulin, record it as one event per day as the total pumped [as basal].

I have had a few questions about using different numbers of insulins and medicines. So here is a brief overview of how these are now handled within Diabetes Logbook X.

There are 2 insulin fields and 1 medicine field, as this seems to be most useful to Type 1 diabetes (which is what we are tracking). However the list of insulins is appended to the list of medicines for the medicines drop down lists and vice versa, so that the 3 fields and their associated defaults can be easily assigned either an insulin or medicine list item.

Insulins and medicine are not handled differently within the application and the distinction is only in the labels on the application interface, which are to help remind the user. Within the reports the 3 different fields are assigned a different colour to aid the reader when scanning the report.

In summary, it is best to assign an insulin/medicine to a specific 'Administered' A/B/C field, if tracking is important for that item: but it won't matter which field, A/B/C, you use.