Skip to forum content

LuxCal Web Calendar

The place for news, questions and suggestions

You are not logged in. Please login or register.

Post new reply

Post new reply

Compose and post your new reply

You may use: BBCode Images Smilies

All fields with bold label must be completed before the form is submitted.

Required information for guests


Required information

Topic review (newest first)

4 Post by stefan

So you were faster than me.
I just came to the forum in order to present my solution smile
Now I'm very interested in yours wink

3 Post by Roel

Hi Stefan,

I could easily solve the "overlap" bug you found.
If you want me to send you the changes, so that you can test it, let me know.

There appeared to be another  bug in the overlap checking: Last occurrence of repeating events not checked for overlap.
Stefan has debugged this problem and has sent me the solution! Thank you Stefan!

The solution for both bugs will be added to the next LuxCal version.

Greetings,
Roel

2 Post by Roel

Hi Stefan,

My point of view is that you are right, it is a bug wink
I will have a thorough look at this, but I don't know if I want to solve this bug. The overlap checking functions are rather complex functions and I don't want to make them much more complex.
However, if there is a way to solve this bug in an easy way, I will solve it.

And yes I agree, it would probably be enough to just check for overlaps in the future. If this will make the functions simpler, I will consider doing this smile

Greetings,
Roel

1 Post by stefan

Hi Roel,

for me it seems like a bug, but perhaps you have another point of view.
My scenario:
There is some kind of repeating event with an category which is not allowed to overlap.
Now I edit one occurrence as single and change - lets say - the venue. After saving this is a single event and the original repeating event will get an entry in the xDates column.

Next step: I edit the original repeating event and save it again.
Now there will be the overlap error message for the date of the event which now is a single event.
But it is not really an overlap because the repeating event has an xDate entry for that date.

I hope that was not to confusing smile

In this context: Wouldn't it be enough for an overlap check to check only events in the future!?
In our calendar there are some repeating events which where started in 2018 - so a lot of years get checked for overlap if those events are edited.

Greetings!