Michael Brand <michael.ch.br...@gmail.com> writes: > When implementing this, consider also whether the END_DATE should be > an agenda entry on its own and of which kind, warning period etc. I > tried to make an example that shows this issue.
Adding to this, as mentioned previously, I interpret the iCal standard to really permit and end *time* rather than an end *date*. Which would make more sense in an org context? Going for an END_TIME parameter, and then comparing exactly to the scheduled time (i.e. if current iteration of the recurring entry > END_TIME, then filter it), or doing an END_DATE and then interpreting the actual cut-off to be at 00:00:00 on that date? -Toke
signature.asc
Description: PGP signature
