I am new to Rainlendar and I am quite satisfied, but I still cannot figure out how it is working...

Well, I set some recurring tasks with following info:

TASK 1
------
Dates: 1/10/2012 to 5/10/2012
Recurrence: 1 year

TASK 2
------
Dates: 6/10/2012 to 31/10/2012
Recurrence: 1 year

TASK 3
------
Dates: 1/10/2012 to 31/10/2012
Recurrence: 1 year

Setting these I get as next recurrence of each task as follows:

For TASK 1 next recurrence on: 1/10/2023 to 5/10/2023
For TASK 2 next recurrence on: 6/10/2013 to 31/10/2013
For TASK 3 next recurrence on: 1/10/2018 to 31/10/2018

Why is that? Why except TASK 2, the other two don't reoccur one year later but reoccurece shows up on years 2018 and 2023??

Welcome to the forum, Hgetis.

I think that you enter something wrong. These dates aren't possible. Another thing is we need more info to say if it's a bug or something else. (version, local or online calendar, etc.)

But to be sure, if it's local, go to your user folder (www.rainlendar.net/cms/index.php?option=com_easyfaq&Itemid=26#faq1), open the [CALENDAR].ics file, search for the tasks by name and paste here the code between BEGIN:VTODO and END:VTODO. Don't try to submit the file if you have stored username or passwords on it (for online calendars).

I have Rainlendar v2.10 32bit.
Why are the above dates wrong? They are in DD/MM/YYYY format.
I use local calendar in i-Calendar (if I remember right the name) format.

This is from the calendar.ics :


The dates I mention in my first post are shown when I mouse over the ToDO list as the date of the next occurence of the task and when I checked it out in the calendar I found the reoccurence in that date (year 2018 and 2023) despite I define as yearly reoccuring task.

This is related to a on-going bug. The alarm says that it was completed on 2017, that is why it shows 2018. I'm not on pc right now, maybe later could give you a better answer

Looking with more details I found this:

For TASK 1, the recurrence rule is RRULE:FREQ=YEARLY;INTERVAL=5;BYMONTHDAY=5;BYMONTH=10
This means that the event repeats in October 5th every 5 years (INTERVAL=5).
There's a bug when marked as completed the first time, that's why it jumps from 2013 (the original end date is 2013-10-05) to 2018.
But I see something strange in the alarm, because it shows for last time 2018-09-30 (but I don't know why) and marked as completed on 2020-10-05. 2020 isn't related to the dates or intervals. Finally, 2018 + 5 = 2023.

TASK 3 is similar. The last alarm is set on 2015 and marked as completed on 2017. Because the interval is 1 year, it shows 2018 as next date.

TASK 2, even showing the right time, still has issues with the last alarm time.

You will need to wait until one of next (beta) builds fix this issue.
Note: this is caused only by the alarms. If you remove it, everything would work fine. Of course, this isn't a solution, but helps to isolate the problem.