MMISoftware Blog
News and views of Mac OS X and iPhone Programming
 
 

iCalMaker updated to 1.6.5

iCalMaker has been updated to 1.6.5

The update includes a number of bug fixes and a few new features.

New Features:

  • Added the option to allow the expansion of repeating events in tab- and comma-delimited export
  • Major improvement to the help system – searching (10.2 and greater) and context-specific (10.3 and greater) help now works correctly

Bug Fixes:

A number of minor bug fixes

  • Recompiled using Xcode 1.2
  • Updated the eSellerate integrated purchase engine

Minor update to iCalMaker in the works!

The way iCalMaker handles repeating events in ‘comma’ and ‘tab’ exports is under consideration again!

This is a tricky one, and one that I have had numerous discussions with users about.

Basically the problem is one of repetition, that is, how should the repeat be shown? Some users have argued that they shouldn’t be broken down, some have argued they should. Some want control over whether they are broken down or not….. (At present the repeating events are not expanded in tab- or comma-delimited exports but are in list exports.)

One point on which we do seem to have agreement is that we can’t agree… and also we have not come to agreement on how repeating events should be broken down, for example, if you have an event that repeats every week forever then when do you stop adding repeating events to the tab/comma output? Five, ten, one hundred?

I think the bottom line is there is no one solution that fits all! And, as a result, it was decided to hold off on a solution until version 2.0 when full preferences would be included.

Now, having said the above, it is currently possible to produce a list of repeating events in the list export. In this case the repeats continue until the first repeat AFTER the last full non-repeating diary entry (and then adds a note that the repeats continue beyond the last date) or until only repeats are left. It would be very easy to ‘activate’ this feature for the comma/tab output as all the code is in place (except for the dialog boxes asking for the format of the output) and just needs to be ‘turned on’ and tested.

Search


 

Subscribe

    Subscribe to MMI news

    Enter your email address:

    Delivered by FeedBurner

    AddThis Social Bookmark Button
 

Categories

 

Archives

 

Spam caught:

 
 

MMISoftware Blog is proudly powered by WordPress
Domain services and hosting by MMISoftware
Entries (RSS) and Comments (RSS).