Keep time periods while importing
26/02/2009 23:25 Filed in: FAQs
The default function during importing data files has
been to ignore any value entered into the time period
data field. The time period is then calculated using
the imported event's time data and the Logbook's User
Settings for start and end periods.
In version 1.1.5 an additional method has been added: import the data file's time periods, if they exist, and only calculate them if they do not. It option is not directly available from within the User Settings or Import window preferences, rather it is a 'hidden' option requiring a UNIX command to be run in Apple's Terminal.app.
To enable this new way of importing time period data open the Terminal.app type in the following command and then press the {return} key:
defaults write com.Nesfield.AsthmaLogbookX ImportTimePeriods YES
If you want to return to the normal way and ignore time periods during import and let the Logbook work them out, do the same as before but use this command:
defaults write com.Nesfield.AsthmaLogbookX ImportTimePeriods NO
This option is kept hidden as it is fairly important that the time period names are kept consistent and mis-typing them in handmade CSV files can cause additional periods to appear, such as:
Night may become NIGHT or night. That would be three time periods.
Having extra unwanted time periods would also impact the layout of the reports with them squashing the data into thin columns.
In version 1.1.5 an additional method has been added: import the data file's time periods, if they exist, and only calculate them if they do not. It option is not directly available from within the User Settings or Import window preferences, rather it is a 'hidden' option requiring a UNIX command to be run in Apple's Terminal.app.
To enable this new way of importing time period data open the Terminal.app type in the following command and then press the {return} key:
defaults write com.Nesfield.AsthmaLogbookX ImportTimePeriods YES
If you want to return to the normal way and ignore time periods during import and let the Logbook work them out, do the same as before but use this command:
defaults write com.Nesfield.AsthmaLogbookX ImportTimePeriods NO
This option is kept hidden as it is fairly important that the time period names are kept consistent and mis-typing them in handmade CSV files can cause additional periods to appear, such as:
Night may become NIGHT or night. That would be three time periods.
Having extra unwanted time periods would also impact the layout of the reports with them squashing the data into thin columns.

